public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52215] __atomic_compare_exchange_n for enumeration type changes signature with -m32 Date: Sun, 12 Feb 2012 14:24:00 -0000 [thread overview] Message-ID: <bug-52215-4-KnGtsDHPgL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52215-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52215 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rejects-valid CC|jwakely.gcc at gmail dot |redi at gcc dot gnu.org |com | Summary|[4.7 Regression] FAIL: |__atomic_compare_exchange_n |ext/profile/mutex_extension |for enumeration type |s_neg.cc (test for excess |changes signature with -m32 |errors) | --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-12 14:23:54 UTC --- It's the second parameter which has the wrong type, this works with -m32: __atomic_compare_exchange_n(&e, e, e, true, __ATOMIC_ACQ_REL, __ATOMIC_RELAXED);
next prev parent reply other threads:[~2012-02-12 14:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-12 13:23 [Bug libstdc++/52215] New: [4.7 Regression] FAIL: ext/profile/mutex_extensions_neg.cc (test for excess errors) dominiq at lps dot ens.fr 2012-02-12 13:57 ` [Bug libstdc++/52215] " redi at gcc dot gnu.org 2012-02-12 14:14 ` [Bug c++/52215] " redi at gcc dot gnu.org 2012-02-12 14:24 ` redi at gcc dot gnu.org [this message] 2012-02-12 20:49 ` [Bug c++/52215] __atomic_compare_exchange_n for enumeration type changes signature with -m32 hp at gcc dot gnu.org 2012-02-13 11:30 ` [Bug c++/52215] [4.7 Regression] " rguenth at gcc dot gnu.org 2012-02-13 14:00 ` jakub at gcc dot gnu.org 2012-02-13 15:28 ` amacleod at redhat dot com 2012-02-13 20:14 ` jakub at gcc dot gnu.org 2012-02-13 20:16 ` jakub 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-52215-4-KnGtsDHPgL@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).