public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/34940] contained subroutines called only once are not inlined Date: Wed, 23 Jan 2008 14:38:00 -0000 [thread overview] Message-ID: <20080123135514.24221.qmail@sourceware.org> (raw) In-Reply-To: <bug-34940-6642@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from rguenth at gcc dot gnu dot org 2008-01-23 13:55 ------- Considering cs1 with 52 insns to be inlined into s1 Estimated growth after inlined into all callees is -13 insns. Estimated badness is 86, frequency 1.00. Not inlining into s1:--param large-stack-frame-growth limit reached. the fortran IO param structure is blowing the stack limit ;) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34940
next prev parent reply other threads:[~2008-01-23 13:55 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-23 13:14 [Bug tree-optimization/34940] New: " jv244 at cam dot ac dot uk 2008-01-23 13:14 ` [Bug tree-optimization/34940] " steven at gcc dot gnu dot org 2008-01-23 14:25 ` rguenth at gcc dot gnu dot org 2008-01-23 14:38 ` rguenth at gcc dot gnu dot org [this message] 2008-01-23 16:21 ` jv244 at cam dot ac dot uk 2008-01-23 17:57 ` jv244 at cam dot ac dot uk 2008-12-29 14:57 ` pinskia at gcc dot gnu dot org [not found] <bug-34940-4@http.gcc.gnu.org/bugzilla/> 2010-11-10 18:04 ` hubicka at gcc dot gnu.org 2010-11-10 18:06 ` hubicka at gcc dot gnu.org 2010-11-10 19:13 ` jakub at gcc dot gnu.org 2010-11-10 22:36 ` hubicka at ucw dot cz 2010-11-10 22:43 ` jakub at gcc dot gnu.org 2010-11-10 22:50 ` hubicka at ucw dot cz 2010-11-10 22:54 ` rguenth at gcc dot gnu.org 2010-11-10 22:55 ` rguenth at gcc dot gnu.org 2010-11-10 23:05 ` hubicka at ucw dot cz 2012-06-29 14:53 ` Joost.VandeVondele at mat dot ethz.ch 2013-03-29 8:58 ` Joost.VandeVondele at mat dot ethz.ch
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=20080123135514.24221.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: linkBe 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).