public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59197] An alias from an always_inline function causes inconsistent behavior Date: Wed, 20 Nov 2013 10:50:00 -0000 [thread overview] Message-ID: <bug-59197-4-jNiU2ecdwp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59197-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59197 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2013-11-20 Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- And with extern void func(void); extern void func(void) __attribute__((alias("alias_target_func"))); extern __inline __attribute__((__always_inline__)) __attribute__((__gnu_inline__)) void func(void) { } extern void alias_target_func(void) {} extern void caller(void) { func(); } you get t.c:4:89: error: redefinition of 'func' extern __inline __attribute__((__always_inline__)) __attribute__((__gnu_inline__)) void func(void) { } ^ t.c:2:13: note: previous definition of 'func' was here extern void func(void) __attribute__((alias("alias_target_func"))); ^ even though I'd say that providing an extern inline definition should still work? But yeah, gnu extern inlines have interesting behavior...
next prev parent reply other threads:[~2013-11-20 10:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-20 1:03 [Bug c/59197] New: " luto at mit dot edu 2013-11-20 10:50 ` rguenth at gcc dot gnu.org [this message] 2024-03-01 23:09 ` [Bug c/59197] " pinskia at gcc dot gnu.org 2024-03-01 23:09 ` pinskia 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-59197-4-jNiU2ecdwp@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).