From: Kai Ruottu <kai.ruottu@wippies.com>
To: "Dr. David Kirkby" <david.kirkby@onetel.net>
Cc: Bill McEnaney <bill@rkirkpat.net>, gcc-help@gcc.gnu.org
Subject: Re: Slow build
Date: Thu, 16 Jul 2009 12:54:00 -0000 [thread overview]
Message-ID: <4A5F23D6.1030103@wippies.com> (raw)
In-Reply-To: <4A5F1776.8010704@onetel.net>
Dr. David Kirkby wrote:
> Bill McEnaney wrote:
>> My Sunblade 100 takes almost 20 hours to build gcc with the machine's
>> 500 MHz UltrSPARC-II processor and its 64-bit bus. So to build that
>> software, I usually launch a batch process with the "batch" command.
>
> I just done it in 37 minutes on a Sun T5240, using 'make -j 100'. I
> could have probably pushed it a bit harder too, as the machine has 128
> hardware threads. This used C, C++ and Fortran.
>
> This was for the 'gcc-4.4.1-RC-20090715' snapshot, which I'm going to
> test, but I doubt gcc 4.4.0 would be too different.
Maybe someone could define what the "build gcc" means here... Even in a
slow 550 MHz P-III PC with Fedora 8 the GCC build for C and C++ took
only 1 h 17 minutes... Some kind of multi-stage build with several
builds for GCC? Not just producing a GCC with the current production
GCC? Like with a crosscompiler...
next prev parent reply other threads:[~2009-07-16 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 20:56 Bill McEnaney
2009-07-15 21:08 ` Tim Prince
2009-07-16 9:26 ` Michael Haubenwallner
2009-07-16 12:05 ` Dr. David Kirkby
2009-07-16 12:54 ` Kai Ruottu [this message]
2009-07-16 12:59 ` Kai Ruottu
2009-07-18 0:07 ` Dr. David Kirkby
-- strict thread matches above, loose matches on Subject: below --
2009-07-21 2:05 Slow Build Benjamin Modra
2009-07-15 20:56 Slow build Dennis Clarke
2009-07-15 20:49 Benjamin Modra
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=4A5F23D6.1030103@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=bill@rkirkpat.net \
--cc=david.kirkby@onetel.net \
--cc=gcc-help@gcc.gnu.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).