public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51258] 64-bit gcc.dg/atomic-compare-exchange-5.c link failure on 32-bit Solaris/x86
Date: Mon, 21 Nov 2011 19:32:00 -0000 [thread overview]
Message-ID: <bug-51258-4-xK2Slpg0tZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51258-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51258
Andrew Macleod <amacleod at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amacleod at redhat dot com
--- Comment #1 from Andrew Macleod <amacleod at redhat dot com> 2011-11-21 19:21:30 UTC ---
32 bit targets don't usually support 128 bit atomic operations natively, and
leave calls to be resolved by an external atomic library. There was some
issue with X32 support where 32 bit could support it under some circumstances.
Now gcc/testsuite/lib/target-supports.exp defines the testsuite check for
whether 128 bit is supported as:
proc check_effective_target_sync_int_128 { } {
if { ([istarget x86_64-*-*] || [istarget i?86-*-*])
&& ![is-effective-target ia32] } {
return 1
} else {
return 0
}
}
I presume if 32 bit solaris isn't supporting 128 bit operations then this needs
to be tweaked...
next prev parent reply other threads:[~2011-11-21 19:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 19:15 [Bug middle-end/51258] New: " ro at gcc dot gnu.org
2011-11-21 19:32 ` amacleod at redhat dot com [this message]
2011-11-21 20:03 ` [Bug middle-end/51258] " rth at gcc dot gnu.org
2011-11-22 15:10 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-22 16:15 ` amacleod at redhat dot com
2011-11-22 18:58 ` ubizjak at gmail dot com
2011-11-22 19:39 ` [Bug testsuite/51258] " ubizjak at gmail dot com
2011-11-22 20:15 ` ubizjak at gmail dot com
2011-11-22 20:22 ` amacleod at redhat dot com
2011-11-23 16:02 ` ro at gcc dot gnu.org
2011-11-24 17:10 ` ro at gcc dot gnu.org
2011-11-25 16:36 ` ubizjak at gmail dot com
2011-11-25 17:19 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-25 18:35 ` uros at gcc dot gnu.org
2011-11-25 20:13 ` uros at gcc dot gnu.org
2011-12-06 19:09 ` howarth at nitro dot med.uc.edu
2011-12-06 19:15 ` howarth at nitro dot med.uc.edu
2011-12-06 19:30 ` ubizjak at gmail dot com
2011-12-06 20:54 ` howarth at nitro dot med.uc.edu
2012-03-22 9:17 ` rguenth at gcc dot gnu.org
2012-03-22 12:26 ` amacleod at redhat dot com
2012-03-22 12:29 ` ro 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-51258-4-xK2Slpg0tZ@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: link
Be 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).