public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44688] [4.6 Regression] Excessive code-size growth at -O3
Date: Mon, 28 Jun 2010 07:46:00 -0000	[thread overview]
Message-ID: <20100628074635.11680.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44688-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from hubicka at gcc dot gnu dot org  2010-06-28 07:46 -------
It really seems that both patches (prefetching and partial inlining) are
responsible for some of the regressions.  I've now comited the patch to reduce
autoinlining from 50 to 40.  It solves size issues at least with -O3
non-FDO/LTO SPECint2000 build.  Unfortunately the tester also shows some
regressions that might turn out to be offnoise.  Lets see how the other
benchmarks go.

I've also switched FDO tester to native testing and plan to enable prefetching
with FDO and -O2 once this change is tested.

Honza


-- 


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


  parent reply	other threads:[~2010-06-28  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27 11:20 [Bug tree-optimization/44688] New: " rguenth at gcc dot gnu dot org
2010-06-27 11:20 ` [Bug tree-optimization/44688] " rguenth at gcc dot gnu dot org
2010-06-28  7:46 ` hubicka at gcc dot gnu dot org [this message]
     [not found] <bug-44688-4@http.gcc.gnu.org/bugzilla/>
2011-01-19 15:49 ` 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=20100628074635.11680.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).