This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/51753] New: Many gcc.dg/simultate-thread tests fail on Solaris 10+/x86
- From: "ro at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 04 Jan 2012 17:25:49 +0000
- Subject: [Bug target/51753] New: Many gcc.dg/simultate-thread tests fail on Solaris 10+/x86
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51753
Bug #: 51753
Summary: Many gcc.dg/simultate-thread tests fail on Solaris
10+/x86
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ro@gcc.gnu.org
CC: ubizjak@gmail.com
Host: i386-pc-solaris2.1[01]
Target: i386-pc-solaris2.1[01]
Build: i386-pc-solaris2.1[01]
Many of the new gcc.dg/simulate-thread tests FAIL on Solaris 10 and 11/x86,
both 32 and 64-bit:
FAIL: gcc.dg/simulate-thread/atomic-other-int.c -O1 -g thread simulation test
FAIL: gcc.dg/simulate-thread/atomic-other-int.c -O2 -g thread simulation test
FAIL: gcc.dg/simulate-thread/atomic-other-int.c -O3 -g thread simulation test
FAIL: gcc.dg/simulate-thread/atomic-other-int.c -Os -g thread simulation test
FAIL: gcc.dg/simulate-thread/atomic-other-longlong.c -O0 -g thread simulation
test
FAIL: gcc.dg/simulate-thread/atomic-other-longlong.c -O1 -g thread simulation
test
FAIL: gcc.dg/simulate-thread/atomic-other-longlong.c -O2 -g thread simulation
test
FAIL: gcc.dg/simulate-thread/atomic-other-longlong.c -O3 -g thread simulation
test
FAIL: gcc.dg/simulate-thread/atomic-other-longlong.c -Os -g thread simulation
test
FAIL: gcc.dg/simulate-thread/atomic-other-short.c -O1 -g thread simulation
test
FAIL: gcc.dg/simulate-thread/atomic-other-short.c -O2 -g thread simulation
test
FAIL: gcc.dg/simulate-thread/atomic-other-short.c -O3 -g thread simulation
test
FAIL: gcc.dg/simulate-thread/atomic-other-short.c -Os -g thread simulation
test
This happens neither on Solaris 8 and 9/x86 (32-bit only), nor on
x86_64-unknown-linux-gnu or i686-unknown-linux-gnu, using gdb 7.3.1 everywhere.
E.g. in atomic-other-int.c, the __atomic_fetch_sub FAILs; if I add logging code
to test_abort, I find
FAIL: invalid intermediate result for value
value = 1 ret = 0
I'm uncertain if this is a code generation issue or a problem on the gdb side.
Rainer