From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Paolo Bonzini <bonzini@gnu.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Chris Lattner <clattner@apple.com>,
Vladimir Makarov <vmakarov@redhat.com>,
"gcc.gcc.gnu.org" <gcc@gcc.gnu.org>,
Evan Cheng <evan.cheng@apple.com>
Subject: Re: New GCC releases comparison and comparison of GCC4.4 and LLVM2.5 on SPEC2000
Date: Wed, 13 May 2009 12:23:00 -0000 [thread overview]
Message-ID: <571f6b510905130457r990e6b6h5afa8579d44484c8@mail.gmail.com> (raw)
In-Reply-To: <20090513114113.GP19296@one.firstfloor.org>
On Wed, May 13, 2009 at 1:41 PM, Andi Kleen <andi@firstfloor.org> wrote:
>> Rather, we should seriously understand what caused the compilation time
>> jump in 4.2, and whether those are still a problem. We made a good job
>> in 4.0 and 4.3 offsetting the slowdowns from infrastructure changes with
>> speedups from other changes; and 4.4 while slower than 4.3 at least
>> stays below 4.2. But, 4.2 was a disaster for compilation time.
>
> Yes that would be useful, although I admit for me personally
> make -j and icecream do a pretty good job at hiding that pain.
Yes, well...
Given the continuous complaints/bashes from some of your fellow kernel
hackers and many others, it still is still important to address the
compilation time issues. There still is enough low-hanging fruit.
Ciao!
Steven
next prev parent reply other threads:[~2009-05-13 11:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 16:27 Vladimir Makarov
2009-05-12 18:05 ` Chris Lattner
2009-05-12 18:21 ` Vladimir Makarov
2009-05-12 19:25 ` Chris Lattner
2009-05-12 22:48 ` Rafael Espindola
2009-05-12 19:41 ` Vladimir Makarov
2009-05-13 12:11 ` Duncan Sands
2009-05-13 12:38 ` Richard Guenther
2009-05-13 12:55 ` Joseph S. Myers
2009-05-13 13:51 ` Duncan Sands
2009-05-26 12:27 ` Chris Lattner
2009-05-26 13:48 ` Vincent Lefevre
2009-05-28 23:00 ` Joseph S. Myers
2009-05-13 20:06 ` Evan Cheng
2009-05-12 18:29 ` Joseph S. Myers
2009-05-12 18:42 ` Vladimir Makarov
2009-05-13 8:44 ` Andi Kleen
2009-05-13 9:56 ` Jakub Jelinek
2009-05-13 11:32 ` Paolo Bonzini
2009-05-13 11:35 ` Paolo Bonzini
2009-05-13 12:07 ` Andi Kleen
2009-05-13 12:23 ` Steven Bosscher [this message]
2009-05-13 12:27 ` Dave Korn
2009-05-13 15:14 ` Paolo Bonzini
2009-05-13 16:16 ` Vladimir Makarov
2009-05-13 17:59 ` Jan Hubicka
2009-05-13 18:11 ` Michael Meissner
2009-05-15 20:19 ` Toon Moene
2009-05-13 6:42 ` Steven Bosscher
2009-05-13 7:33 ` Paolo Bonzini
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=571f6b510905130457r990e6b6h5afa8579d44484c8@mail.gmail.com \
--to=stevenb.gcc@gmail.com \
--cc=andi@firstfloor.org \
--cc=bonzini@gnu.org \
--cc=clattner@apple.com \
--cc=evan.cheng@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=vmakarov@redhat.com \
/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).