From: Matt Austern <austern@apple.com>
To: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
Cc: gcc@gcc.gnu.org
Subject: Re: Huge compile time & run time performance regression 3.3 -> HEAD
Date: Mon, 19 May 2003 16:18:00 -0000 [thread overview]
Message-ID: <110B848B-8A12-11D7-B0E8-000393B2ABA2@apple.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305181734000.457-100000@goofy>
On Sunday, May 18, 2003, at 08:45 AM, Richard Guenther wrote:
> Hi!
>
> As 3.3 is now out, I start comparing 3.3 to HEAD wrt compile time
> performance and performance of the resulting code. As always these
> comparisons are for a POOMA based scientific application.
>
> I experience a 100% compile time regression (673.50s -> 1284.48s) and
> a 12% runtime performance regression (150s -> 171s) when comparing
> gcc3.3 to HEAD.
>
> Time reports follow, the most prominent regressions are expand, global
> CSE
> (>300%!), loop analysis and branch prediction.
>
> Compile options are -ftemplate-depth-80 -fno-exceptions -O2
> -march=athlon
> -funroll-loops -fomit-frame-pointer
Do you see any compile time regressions at -O0?
(I'm asking for the obvious reason: trying to find out how much work we
need to do in the front end as opposed to the back end.)
--Matt
next prev parent reply other threads:[~2003-05-19 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 16:10 Richard Guenther
2003-05-18 19:22 ` Richard Guenther
2003-05-18 19:31 ` Richard Guenther
2003-05-18 19:35 ` Richard Guenther
2003-05-19 16:18 ` Matt Austern [this message]
2003-05-19 19:01 ` Richard Guenther
2003-05-19 20:51 ` Richard Guenther
2003-05-19 21:04 ` Gabriel Dos Reis
2003-05-19 21:10 ` Richard Guenther
2003-05-19 21:14 ` Gabriel Dos Reis
2003-05-19 21:24 ` Richard Guenther
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=110B848B-8A12-11D7-B0E8-000393B2ABA2@apple.com \
--to=austern@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenth@tat.physik.uni-tuebingen.de \
/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).