9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gaute B Strokkenes <gs234@cam.ac.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] p9/linux/fbsd compiler shootout
Date: Mon,  4 Mar 2002 10:04:36 +0000	[thread overview]
Message-ID: <4aadtqj28c.fsf@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20020226150031.A2A4B19A1C@mail.cse.psu.edu>

On Tue, 26 Feb 2002, andrey@lanl.gov 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.
> 
>> A total curiosity is that running the Linux binaries under
>> emulation in BSD is *faster* than running the native BSD binaries.
>> It's hard to imagine that the BSD team specially optimized that
>> case, does anyone have any knowledge or guesses?
>> 
> 
> gcc 3.0 on FBSD was locally compiled and installed (as was noted in
> the explanations), had it been taken from a binary package it _must_
> have been much faster (all we did was 'make; make install')...

Read the GCC installation manual: you're supposed to say "make
bootstrap", not just "make".  IIRC if you just use plain "make" what
you get is a compiler that is built with the system default compiler.
If you use "make bootstrap", then GCC is first built with the system
compiler, then that compiler is used to compile GCC again.  Then that
compiler builds GCC a third and final time.  The last two compilers
are compared byte-for-byte; they should be equal since GCC should
produce identical output independent of what compiler it is built
with.

-- 
Gaute Strokkenes                        http://www.srcf.ucam.org/~gs234/
I joined scientology at a garage sale!!


  parent reply	other threads:[~2002-03-04 10:04 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
2002-02-26 18:00   ` splite
2002-02-26 16:04 ` Matt H
2002-03-04 10:04 ` Gaute B Strokkenes [this message]
  -- 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=4aadtqj28c.fsf@kern.srcf.societies.cam.ac.uk \
    --to=gs234@cam.ac.uk \
    --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).