public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/46596] misbehavior when mixing always_inline and alias attributes in the same compilation unit Date: Wed, 29 Feb 2012 16:22:00 -0000 [thread overview] Message-ID: <bug-46596-4-vb5NtswdKP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46596-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46596 Mike Frysinger <vapier at gentoo dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |toolchain at gentoo dot org See Also| |http://sourceware.org/bugzi | |lla/show_bug.cgi?id=10375 --- Comment #6 from Mike Frysinger <vapier at gentoo dot org> 2012-02-29 16:13:44 UTC --- (In reply to comment #4) yes, the source of this bug was the glibc code which i reduced even further into the testcase posted originally (In reply to comment #5) if gcc-4.7 works fine with the proposed code, then i'm fine with that. we already have workarounds in place for those.
next prev parent reply other threads:[~2012-02-29 16:14 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-22 3:50 [Bug c/46596] New: " vapier at gentoo dot org 2010-11-22 4:58 ` [Bug c/46596] " vapier at gentoo dot org 2010-11-22 11:11 ` rguenth at gcc dot gnu.org 2010-11-22 19:02 ` vapier at gentoo dot org 2012-02-29 9:44 ` jyasskin at gcc dot gnu.org 2012-02-29 15:16 ` hubicka at ucw dot cz 2012-02-29 16:22 ` vapier at gentoo dot org [this message] 2024-03-01 23:09 ` [Bug ipa/46596] " 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-46596-4-vb5NtswdKP@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).