public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/45267] [4.5 regression] inlining fails with -m32
Date: Thu, 12 Aug 2010 22:08:00 -0000	[thread overview]
Message-ID: <20100812220837.23893.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45267-17603@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from kretz at kde dot org  2010-08-12 22:08 -------
Right, but then I probably have two bugs to report:
1. always_inline is not honored (heuristics are applied even though they
shouldn't)
2. inlining of small functions does not work reliably (i.e. a function declared
with "inline" and containing just one ore two instructions is discarded for
inlining by GCC). I think I've seen this on earlier compiler versions too -
which is why I added the always_inline attributes in the first place. I've
never been able to reduce a testcase, though.

I believe this testcase shows both problems, no?


-- 


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


  parent reply	other threads:[~2010-08-12 22:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 16:15 [Bug middle-end/45267] New: " kretz at kde dot org
2010-08-12 18:17 ` [Bug middle-end/45267] " rguenth at gcc dot gnu dot org
2010-08-12 19:09 ` hjl dot tools at gmail dot com
2010-08-12 20:17 ` hjl dot tools at gmail dot com
2010-08-12 21:07 ` steven at gcc dot gnu dot org
2010-08-12 21:17 ` kretz at kde dot org
2010-08-12 21:31 ` steven at gcc dot gnu dot org
2010-08-12 21:35 ` rguenth at gcc dot gnu dot org
2010-08-12 21:49 ` rguenth at gcc dot gnu dot org
2010-08-12 22:08 ` kretz at kde dot org [this message]
2010-08-12 22:16 ` [Bug c++/45267] " rguenth at gcc dot gnu dot org
2010-08-30 15:57 ` rguenth at gcc dot gnu dot 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=20100812220837.23893.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).