From: "William K. Josephson" <jkw@morphisms.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] GCC3.0 [Was; Webbrowser]
Date: Thu, 6 Feb 2003 13:10:09 -0500 [thread overview]
Message-ID: <20030206181009.GA42953@mero.morphisms.net> (raw)
In-Reply-To: <1d03b9df37f6a72c3d2d7dcaec3f3c9d@plan9.bell-labs.com>
On Thu, Feb 06, 2003 at 12:32:52PM -0500, David Presotto wrote:
>themselves were not at all OS tests, they pretty much test the compiler
>and malloc and nothing else. There's a little pipe stuff in there to implement
>locks but they looked like pretty high level locks.
Not to mention that the repeated comparisons with gcc
get tiresome: gcc is really not as great as many proponents
make it out to be, even on the ia32. I'm very glad to have
it and use it regularly, but it is much slower than either
8c or the vendor compiler and generates substantially slower
code than the vendor compiler, at least in my experience.
It isn't uncommon to see Intel's compiler beat gcc by 30-40%
and I haven't found any non-trivial examples where gcc beats
the Microsoft or Intel compilers, although they may well
exist. If someone has the time, money, and warm bodies to
invest, great, otherwise I'll port a few assembly routines
when it really matters and get on with my life. Premature
obfusc^H^H^H^H^Hoptimization is the root of all evil.
next prev parent reply other threads:[~2003-02-06 18:10 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 20:44 [9fans] Webbrowser Keith Nash
2003-02-05 22:27 ` John Packer
2003-02-05 22:55 ` Skip Tavakkolian
2003-02-06 0:53 ` John Packer
2003-02-06 1:19 ` Russ Cox
2003-02-06 3:00 ` [9fans] GCC3.0 [Was; Webbrowser] andrey mirtchovski
2003-02-06 4:16 ` andrey mirtchovski
2003-02-06 14:24 ` David Presotto
2003-02-06 15:30 ` andrey mirtchovski
2003-02-06 17:32 ` David Presotto
2003-02-06 18:10 ` William K. Josephson [this message]
2003-02-06 18:16 ` Ronald G. Minnich
2003-02-06 18:23 ` William K. Josephson
2003-02-06 21:09 ` Ronald G. Minnich
2003-02-06 12:30 ` [9fans] Webbrowser - porting mozilla matt
2003-02-06 12:52 ` Ian Broster
2003-02-06 2:13 ` [9fans] Webbrowser Peter Bosch
2003-02-06 5:28 [9fans] GCC3.0 [Was; Webbrowser] okamoto
2003-02-06 5:40 ` andrey mirtchovski
2003-02-06 15:15 ` Ronald G. Minnich
2003-02-06 15:39 ` Tharaneedharan Vilwanathan
2003-02-06 15:45 ` Ronald G. Minnich
2003-02-06 16:31 ` rob pike, esq.
2003-02-06 16:36 ` rob pike, esq.
2003-02-06 16:56 ` matt
2003-02-06 17:11 ` Ronald G. Minnich
2003-02-06 17:25 ` Tharaneedharan Vilwanathan
2003-02-06 17:32 ` andrey mirtchovski
2003-02-06 17:44 ` Sam
2003-02-06 18:07 ` Ronald G. Minnich
2003-02-06 18:14 ` David Presotto
2003-02-06 18:17 ` Ronald G. Minnich
2003-02-06 20:36 ` Dean Prichard
2003-02-06 18:35 ` andrey mirtchovski
2003-02-06 18:43 ` David Presotto
2003-02-06 19:12 ` David Presotto
2003-02-06 19:20 ` Scott Schwartz
2003-02-06 17:23 ` David Butler
2003-02-06 17:50 C H Forsyth
2003-02-06 18:08 ` Ronald G. Minnich
2003-02-06 20:13 Keith Nash
2003-02-06 21:29 ` Tharaneedharan Vilwanathan
2003-02-06 21:33 ` Russ Cox
2003-02-06 21:40 ` Jack Johnson
2003-02-07 8:44 ` Richard Miller
2003-02-07 13:51 ` matt
2003-02-07 14:03 ` Boyd Roberts
2003-02-07 0:06 ` Geoff Collyer
2003-02-07 5:32 ` Skip Tavakkolian
2003-02-07 1:46 okamoto
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=20030206181009.GA42953@mero.morphisms.net \
--to=jkw@morphisms.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).