From: "Wilhelm B. Kloke" <wb@vestein.arb-phys.uni-dortmund.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] p9/linux/fbsd compiler shootout
Date: Tue, 26 Feb 2002 16:02:05 +0000 [thread overview]
Message-ID: <a5g9o8$t0i$1@yorikke.arb-phys.uni-dortmund.de> (raw)
In-Reply-To: <20020226150031.A2A4B19A1C@mail.cse.psu.edu>
In article <20020226150031.A2A4B19A1C@mail.cse.psu.edu>,
andrey mirtchovski <9fans@cse.psu.edu> wrote:
>> The compile time using for the BSD/2.95/no test looks *really* low;
>> are we sure about that number? It's a very strange outlier, isn't it?
>> I'll mostly ignore that one, because it is *such* a surprise; GCC
>> isn't normally thought to be that fast, but hey, maybe it really is.
>>
>
>several more tests yield exactly the same results -- FBSD 4.5 w/
>gcc2.95 takes about 18 seconds to compile.
Surprise diminishes, when you take the difference between gcc2.95 and 2.96
into account (linux was tested with the latter). 2.96 is 3.00-beta
(in fact, 2.96 was never recommended for use and made it into some
Linux distributions only accidentally.)
--
Dipl.-Math. Wilhelm Bernhard Kloke
Institut fuer Arbeitsphysiologie an der Universitaet Dortmund
Ardeystrasse 67, D-44139 Dortmund, Tel. 0231-1084-257
next prev parent reply other threads:[~2002-02-26 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 15:02 andrey mirtchovski
2002-02-26 16:02 ` Wilhelm B. Kloke [this message]
2002-02-26 18:00 ` splite
2002-02-26 16:04 ` Matt H
2002-03-04 10:04 ` Gaute B Strokkenes
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 14:20 rob pike
2002-02-26 16:07 ` Sean Quinlan
2002-02-26 14:18 rob pike
2002-02-26 11:15 forsyth
2002-02-26 3:10 rob pike
2002-02-26 10:26 ` Thomas Bushnell, BSG
2002-02-26 3:05 andrey mirtchovski
2002-02-26 10:27 ` Thomas Bushnell, BSG
2002-02-26 10:27 ` Thomas Bushnell, BSG
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='a5g9o8$t0i$1@yorikke.arb-phys.uni-dortmund.de' \
--to=wb@vestein.arb-phys.uni-dortmund.de \
--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).