From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "ridiculous benchmarks"-r-us
Date: Fri, 9 Jan 2004 20:29:37 +0000 [thread overview]
Message-ID: <473f99eea04976b0758b7170409ea0d8@terzarima.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0401091521480.4947-100000@athena>
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
worse, i've had gcc fanatics work themselves up into a terrible
state about how presumptious it was for Plan 9 C to add its own extensions.
since i've historically been troubled more by bugs in gcc than
bugs in Plan 9's C, i've not been much impressed.
[-- Attachment #2: Type: message/rfc822, Size: 2103 bytes --]
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] "ridiculous benchmarks"-r-us
Date: Fri, 9 Jan 2004 15:25:26 -0500 (EST)
Message-ID: <Pine.LNX.4.30.0401091521480.4947-100000@athena>
> I'd rather go with APE than with gcc ;)
A really fair default considering:
http://gcc.gnu.org/onlinedocs/gcc/C-Extensions.html#C%20Extensions
With all they put in you'd think plan 9's extensions would
have been consumed by now. Must be the license.
Sam
next prev parent reply other threads:[~2004-01-09 20:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 17:42 mirtchov
2004-01-09 17:47 ` ron minnich
2004-01-09 18:19 ` Icarus Sparry
2004-01-09 18:37 ` mirtchov
2004-01-09 20:25 ` Sam
2004-01-09 20:29 ` Charles Forsyth [this message]
2004-01-09 20:44 ` Sam
2004-01-09 20:44 ` Brantley Coile
2004-01-10 0:37 ` Dennis Ritchie
2004-01-09 20:48 ` mirtchov
2004-01-11 1:02 ` [9fans] 'ridiculous benchmarks'-r-us Joel Salomon
2004-01-09 18:52 ` [9fans] "ridiculous benchmarks"-r-us Brantley Coile
2004-01-09 20:06 ` Tristan Seligmann
2004-01-10 5:06 ` boyd, rounin
2004-01-09 19:40 ` Roman Shaposhnick
2004-01-09 20:54 ` Atanas Bachvaroff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=473f99eea04976b0758b7170409ea0d8@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).