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 c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution Date: Thu, 10 May 2007 10:04:00 -0000 [thread overview] Message-ID: <20070510100434.17162.qmail@sourceware.org> (raw) In-Reply-To: <bug-31886-14209@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rguenth at gcc dot gnu dot org 2007-05-10 11:04 ------- Confirmed. Either we should not accept always_inline on a function not declared inline (or warn in that case), or a function marked always_inline should be considered for inlining always. Second, the t.i:3: sorry, unimplemented: inlining failed in call to 'alloc_null_binding1': function body not available is fixed in 4.1.2. Which leaves us with t.i:3: sorry, unimplemented: inlining failed in call to 'alloc_null_binding1': function not inlinable with the function not marked inline (but only for -O0, not -O). I guess we want to make that behavior at least consistent. Note with -O0 -finline we get t.i:3: sorry, unimplemented: inlining failed in call to 'alloc_null_binding1': function body not available again ;) -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu dot | |org, hubicka at gcc dot gnu | |dot org Status|WAITING |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2007-05-10 11:04:34 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
next prev parent reply other threads:[~2007-05-10 10:04 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-10 3:07 [Bug c/31886] New: " zhouyi04 at ios dot cn 2007-05-10 3:19 ` [Bug c/31886] " pinskia at gcc dot gnu dot org 2007-05-10 3:41 ` zhouzhouyi at ercist dot iscas dot ac dot cn 2007-05-10 3:43 ` zhouzhouyi at ercist dot iscas dot ac dot cn 2007-05-10 4:33 ` zhouyi04 at ios dot cn 2007-05-10 10:04 ` rguenth at gcc dot gnu dot org [this message] 2007-08-02 17:18 ` rob1weld at aol dot com 2007-08-02 17:24 ` rob1weld at aol dot com 2007-08-06 6:45 ` rob1weld at aol dot com 2007-08-06 8:41 ` zhouyi04 at ios dot cn 2007-08-20 7:58 ` rguenth at gcc dot gnu dot org 2009-01-13 22:10 ` rob1weld at aol dot com 2009-01-13 22:41 ` 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=20070510100434.17162.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).