public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10196: [3.3/3.4 regression] Compile time regression with inlining
Date: Tue, 08 Apr 2003 11:06:00 -0000	[thread overview]
Message-ID: <20030408110601.27032.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/10196; it has been noted by GNATS.

From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
To: gcc-gnats@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, <nobody@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>
Subject: Re: optimization/10196: [3.3/3.4 regression] Compile time regression
 with inlining
Date: Tue, 8 Apr 2003 12:59:06 +0200 (CEST)

 The problem seems to come from changes in exception handling between
 3.2 and 3.3. If I specify -fno-exceptions the compile time regression
 between 3.2 and 3.3 reduces to 8.6s vs. 10s total time, without
 -fno-exceptions it is 10s vs. 146s (otherwise just -O2). The same
 testcase compiled with -fno-exceptions (libstdc++ stuff differs and
 is incompatible) can be fetched at
 
 http://www.tat.physik.uni-tuebingen.de/~rguenth/DynamicLayout.cmpl.ii.noex.gz
 
 I'm now trying to collect profiles for both cases
 
 Richard.
 
 --
 Richard Guenther <richard dot guenther at uni-tuebingen dot de>
 WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/
 


             reply	other threads:[~2003-04-08 11:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 11:06 Richard Guenther [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-23 15:46 mmitchel
2003-04-08 14:46 Richard Guenther
2003-04-08 11:06 Steven Bosscher
2003-04-08  9:56 Steven Bosscher
2003-04-07 15:06 Steven Bosscher
2003-03-24 18:26 mmitchel
2003-03-24 13:46 Richard Guenther
2003-03-24  8:36 mmitchel

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=20030408110601.27032.qmail@sources.redhat.com \
    --to=rguenth@tat.physik.uni-tuebingen.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).