public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/49139] always_inline attribute inconsistencies Date: Tue, 24 May 2011 13:28:00 -0000 [thread overview] Message-ID: <bug-49139-4-AAsbeEfQoy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49139-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49139 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-05-24 12:54:20 UTC --- You forgot to add inline keyword, always_inline attribute makes no sense on functions without inline keyword (or C++ methods defined in class).
next prev parent reply other threads:[~2011-05-24 13:26 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-24 12:55 [Bug regression/49139] New: " chrbr at gcc dot gnu.org 2011-05-24 13:28 ` jakub at gcc dot gnu.org [this message] 2011-05-24 13:34 ` [Bug regression/49139] " rguenth at gcc dot gnu.org 2011-05-24 15:13 ` chrbr at gcc dot gnu.org 2011-05-24 15:48 ` [Bug middle-end/49139] " manu at gcc dot gnu.org 2011-05-24 16:26 ` chrbr at gcc dot gnu.org 2011-05-27 14:38 ` [Bug middle-end/49139] always_inline attribute inconsistencies on failure chrbr at gcc dot gnu.org 2011-05-27 14:38 ` [Bug middle-end/49139] always_inline attribute inconsistencies chrbr at gcc dot gnu.org 2011-05-27 14:39 ` [Bug middle-end/49139] always_inline attribute inconsistencies on failure chrbr at gcc dot gnu.org 2011-05-27 15:11 ` manu at gcc dot gnu.org 2011-06-21 6:42 ` chrbr at gcc dot gnu.org 2011-06-21 6:44 ` chrbr at gcc dot gnu.org 2011-06-21 6:45 ` chrbr at gcc dot gnu.org 2011-06-21 6:49 ` chrbr at gcc dot gnu.org 2011-07-11 13:03 ` chrbr 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-49139-4-AAsbeEfQoy@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: 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).