public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/36439] [4.3 Regression] very long compile-time in PRE building gimp-plugin-registry
Date: Fri, 19 Mar 2010 10:09:00 -0000	[thread overview]
Message-ID: <20100319100914.3349.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36439-5724@http.gcc.gnu.org/bugzilla/>



------- Comment #14 from rguenther at suse dot de  2010-03-19 10:09 -------
Subject: Re:  [4.3 Regression] very long
 compile-time in PRE building gimp-plugin-registry

On Fri, 19 Mar 2010, kurt at garloff dot de wrote:

> ------- Comment #11 from kurt at garloff dot de  2010-03-19 00:34 -------
> (In reply to comment #10)
> > GCC 4.3.4 is being released, adjusting target milestone.
> 
> Very non-scientific benchmark:
> Did compile latest gmic-1.3.4.0 on a 2xL5540 system (plenty of RAM) with make
> -j8 and compile flags: 
> -O3 --param max-inline-insns-auto=200 -ffast-math -funroll-loops
> -ftree-vectorize
> Times (in seconds, user, elapsed):
> 4.3.5:             1263u, 377e
>  w/ -fno-tree-pre:  755u, 202e
> 4.4.4:             1022u, 311e
>  w/ -fno-tree-pre:  996u, 284e
> 4.5.0:             2325u, 615e
>  w/ -fno-tree-pre: 1974u, 543e
> 
> Note that this is in contrast to earlier observations that 4.4/4.5 did do much
> better than 4.3. Don't know whether that's caused by changed gmic code or
> whether we have regressed in 4.5. Let me know if you want me to pick one file
> that takes particularly long to compile and investigate further.

This bug was about PRE causing compile-time issues at -O2 which is
what was investigated and fixed for the testcases attached to this PR.

I see, for -O2 and the CImg.C testcase (just using openSUSE packages
from devel:gcc):

4.3.4 (r152973): stopped after 4min
4.4.2 (r155966): 68s
4.5.0 (r157384): 74s

also see PR43415 for a similar problem where I am about to commit a
patch.

If you can provide a testcase for plain -O3 [-ffast-math -funroll-loops] 
being slow it would be appropriate to open a new bugreport for it.

Thanks,
Richard.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36439


  parent reply	other threads:[~2010-03-19 10:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 11:00 [Bug c++/36439] New: [4.3 regression] infinite loop " debian-gcc at lists dot debian dot org
2008-06-05 11:24 ` [Bug c++/36439] [4.3/4.4 Regression] infinite loop in PRE " rguenth at gcc dot gnu dot org
2008-06-05 11:38 ` rguenth at gcc dot gnu dot org
2008-06-05 11:38 ` rguenth at gcc dot gnu dot org
2008-06-05 12:55 ` [Bug tree-optimization/36439] " pinskia at gcc dot gnu dot org
2008-06-06 15:05 ` rguenth at gcc dot gnu dot org
2008-06-07 14:40 ` dirtyepic at gentoo dot org
2008-06-13 21:44 ` mmitchel at gcc dot gnu dot org
2008-08-27 22:09 ` jsm28 at gcc dot gnu dot org
2008-11-02 12:34 ` [Bug tree-optimization/36439] [4.3 " rguenth at gcc dot gnu dot org
2008-11-02 12:50 ` rguenth at gcc dot gnu dot org
2009-01-24 10:24 ` [Bug tree-optimization/36439] [4.3 Regression] very long compile-time " rguenth at gcc dot gnu dot org
2009-02-19 19:57 ` steven at gcc dot gnu dot org
2009-08-04 12:40 ` rguenth at gcc dot gnu dot org
2010-03-19  0:35 ` kurt at garloff dot de
2010-03-19  0:36 ` pinskia at gcc dot gnu dot org
2010-03-19  8:03 ` kurt at garloff dot de
2010-03-19 10:09 ` rguenther at suse dot de [this message]
2010-03-19 10:15 ` rguenth at gcc dot gnu dot org
2010-05-22 18:24 ` rguenth at gcc dot gnu dot org
     [not found] <bug-36439-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 11:35 ` rguenth at gcc dot gnu.org

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=20100319100914.3349.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).