From: Justin Piszcz <war@starband.net>
To: linux-kernel@vger.kernel.org
Subject: gcc-2.95.3 vs gcc-3.0.4
Date: Fri, 22 Feb 2002 23:40:09 -0500 [thread overview]
Message-ID: <3C771D29.942A07C2@starband.net> (raw)
Wow, not sure if anyone here has done any benchmarks, but look at these
build times:
Kernel 2.4.17 did compile with 3.0.4, just much much slower than 2.95.3
however.
GCC 2.95.3
Boot sector 512 bytes.
Setup is 2628 bytes.
System is 899 kB
make[1]: Leaving directory `/usr/src/linux-2.4.17/arch/i386/boot'
287.28user 23.99system 5:15.81elapsed 98%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (514864major+684661minor)pagefaults 0swaps
GCC 3.0.4
Boot sector 512 bytes.
Setup is 2628 bytes.
System is 962 kB
warning: kernel is too big for standalone boot from floppy
make[1]: Leaving directory `/usr/src/linux-2.4.17/arch/i386/boot'
406.87user 28.38system 7:23.68elapsed 98%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (546562major+989237minor)pagefaults 0swaps
next reply other threads:[~2002-02-23 4:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 4:40 Justin Piszcz [this message]
2002-02-23 4:44 ` gcc-2.95.3 vs gcc-3.0.4 Larry McVoy
2002-02-23 5:13 ` Justin Piszcz
2002-02-23 5:22 ` Andrew Morton
2002-02-23 5:50 ` Richard Gooch
2002-02-23 10:31 ` Benny Sjostrand
2002-02-23 15:00 ` Martin Dalecki
2002-02-25 8:07 ` Simon Kirby
2002-02-25 8:15 ` David S. Miller
2002-02-25 8:32 ` David Rees
2002-02-25 9:32 ` Ian Castle
2002-02-25 9:52 ` Markus Schaber
2002-02-23 5:40 ` hugang
2002-02-23 5:56 ` Andrew Morton
2002-02-23 9:25 ` Paul G. Allen
2002-02-23 13:55 ` gmack
2002-02-23 15:43 ` bert hubert
2002-02-25 0:07 ` Luigi Genoni
2002-02-25 0:32 ` ANN: syscalltrack v0.7 released guy keren
2002-02-25 7:48 ` gcc-2.95.3 vs gcc-3.0.4 Jakub Jelinek
2002-02-25 9:46 ` Luigi Genoni
2002-02-25 9:59 ` Jakub Jelinek
2002-02-25 12:55 ` Jan Hubicka
2002-02-25 16:08 ` Juan Quintela
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=3C771D29.942A07C2@starband.net \
--to=war@starband.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.