From: Toon Moene <toon@moene.org>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: Steven Bosscher <stevenb.gcc@gmail.com>,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Where does the time go?
Date: Thu, 20 May 2010 19:57:00 -0000 [thread overview]
Message-ID: <4BF59435.7090505@moene.org> (raw)
In-Reply-To: <4BF58AE0.3090103@redhat.com>
On 05/20/2010 09:17 PM, Vladimir Makarov wrote:
> Steven Bosscher wrote:
>> For some time now, I've wanted to see where compile time goes in a
>> typical GCC build, because nobody really seems to know what the
>> compiler spends its time on. The impressions that get published about
>> gcc usually indicate that there is at least a feeling that GCC is not
>> getting faster, and that parts of the compiler are unreasonably slow.
> It is just a feeling. In fact, starting since 4.2, gcc becomes faster
> (if we ignore LTO). My feeling is that LLVM becomes slower. The gap in
> compilation speed between GCC4.5 and LLVM2.7 achieves less 10% on x86_64
> SPECInt2000 for -O2.
>
> Feeling that GCC becomes slower probably occurs for people who switched
> recently from 3.x versions because in comparison with theses versions
> gcc became slower achieving maximum slowdown 25 and 40% slowdown on
> gcc4.2 correspondingly on SPECInt2000 and SPECFP2000 on x86_64 for -O2.
I never understood the problem of "gcc getting slower", but that might
just be my "the economic life-time of computers is 3 years" replacement
policy.
It's very interesting, Vladimir, to couple this to switching from gcc 3
to gcc 4.
Because I was mainly interested in what gcc 4 (+ gfortran) could *do*
(in terms of the code it could compile), I never really bothered about
the compiler's speed of doing so.
What I *did* notice, though, is that as of gcc 4.4, I can recompile our
complete weather forecasting code (~ 1 million lines of Fortran and ~
30,000 lines of C) with -O3 -ffast-math (therefore, with vectorization)
within 5 minutes [quad core Core 2].
This means that recompiling "everything" before every run (4 times a
day) is now a no-brainer (currently, I do it only once a day, max).
--
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html#Fortran
next prev parent reply other threads:[~2010-05-20 19:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 15:55 Steven Bosscher
2010-05-20 19:16 ` Vladimir Makarov
2010-05-20 19:57 ` Toon Moene [this message]
2010-05-20 20:36 ` Steven Bosscher
2010-05-20 20:54 ` Duncan Sands
2010-05-20 21:14 ` Steven Bosscher
2010-05-23 19:09 ` Joseph S. Myers
2010-05-24 17:00 ` Mark Mitchell
2010-05-24 21:07 ` Steven Bosscher
2010-05-24 23:22 ` Mark Mitchell
2010-05-25 1:20 ` Joseph S. Myers
2010-05-20 21:09 ` Ian Lance Taylor
2010-05-20 21:14 ` Xinliang David Li
2010-05-20 21:18 ` Steven Bosscher
2010-05-20 21:21 ` Xinliang David Li
2010-05-21 10:54 ` Richard Guenther
2010-05-21 13:26 ` Jan Hubicka
2010-05-21 15:06 ` Richard Guenther
2010-05-21 15:49 ` Jan Hubicka
2010-05-21 17:06 ` Xinliang David Li
2010-05-21 17:07 ` Richard Guenther
2010-05-20 19:36 ` Joseph S. Myers
2010-05-20 20:35 ` Eric Botcazou
2010-05-20 20:42 ` Eric Botcazou
2010-05-21 20:43 ` Diego Novillo
2010-05-20 21:28 Bradley Lucier
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=4BF59435.7090505@moene.org \
--to=toon@moene.org \
--cc=gcc@gcc.gnu.org \
--cc=stevenb.gcc@gmail.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).