public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49997] [4.7 Regression] ICE in inline_small_functions with -fnon-call-exceptions
Date: Sun, 11 Sep 2011 10:06:00 -0000	[thread overview]
Message-ID: <bug-49997-4-145QVvOC2P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49997-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jan Hubicka <hubicka at ucw dot cz> 2011-09-11 09:42:32 UTC ---
> Possibly. Last time I tried it it however lead to bigger and slower binaries.
> Well, I will patch frescobaldi today and lets see.
OK, removing this trick alone regress tramp3d by about 80%,and capacita by
about 15%.
Causes small regression on wave & nbench.
reduces size a bit for dlv.

The reason for this is to drive heuristic to preffer functions that can
ultimately be fully inlined wihtout much of effort.  Frankly I think this makes
sense.  We could of course reach this otherwise. Like compute expected growths
just once
and expect that other inlining won't affect them in important way (that si
wrong of course)
and/or just cut the update algorithm by fixed threshold allowing priority queue
to ba
partly out of date when we run into the most expensive cases.

Honza


  parent reply	other threads:[~2011-09-11  9:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 21:55 [Bug tree-optimization/49997] New: " arthur.j.odwyer at gmail dot com
2011-08-08  9:44 ` [Bug tree-optimization/49997] [4.7 Regression] " rguenth at gcc dot gnu.org
2011-09-06 14:06 ` hubicka at gcc dot gnu.org
2011-09-06 15:49 ` rguenth at gcc dot gnu.org
2011-09-09  9:06 ` hubicka at ucw dot cz
2011-09-11 10:06 ` hubicka at ucw dot cz [this message]
2011-10-10 12:13 ` rguenth at gcc dot gnu.org
2011-12-06 13:45 ` rguenth at gcc dot gnu.org
2011-12-06 13:46 ` 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=bug-49997-4-145QVvOC2P@http.gcc.gnu.org/bugzilla/ \
    --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).