public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/53284] New: Several libatomic tests fail on 32-bit Solaris/x86
Date: Tue, 08 May 2012 16:23:00 -0000 [thread overview]
Message-ID: <bug-53284-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53284
Bug #: 53284
Summary: Several libatomic tests fail on 32-bit Solaris/x86
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: ro@gcc.gnu.org
CC: rth@gcc.gnu.org
Host: i386-pc-solaris2.9, i386-pc-solaris2.1[01]
Target: i386-pc-solaris2.9, i386-pc-solaris2.1[01]
Build: i386-pc-solaris2.9, i386-pc-solaris2.1[01]
With the libatomic build problems on Solaris out of the way, there remain a
couple
of testsuite failures for the default 32-bit multilib:
FAIL: libatomic.c/atomic-compare-exchange-4.c execution test
FAIL: libatomic.c/atomic-exchange-4.c execution test
FAIL: libatomic.c/atomic-load-4.c execution test
FAIL: libatomic.c/atomic-op-4.c execution test
FAIL: libatomic.c/atomic-store-4.c execution test
FAIL: libatomic.c/generic-2.c execution test
It seems all of them SEGV, e.g.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 1)]
0xfef823f7 in libat_compare_exchange_8 (mptr=0x8049e68, eptr=0x8049e70,
newval=18446744073709551615, smodel=5, fmodel=0) at
/vol/gcc/src/hg/trunk/local/libatomic/cas_n.c:41
(gdb) where
#0 0xfef823f7 in libat_compare_exchange_8 (mptr=0x8049e68, eptr=0x8049e70,
newval=18446744073709551615, smodel=5, fmodel=0) at
/vol/gcc/src/hg/trunk/local/libatomic/cas_n.c:41
#1 0xfef823fc in libat_compare_exchange_8 (mptr=0x8049e68, eptr=0x8049e70,
newval=18446744073709551615, smodel=5, fmodel=0) at
/vol/gcc/src/hg/trunk/local/libatomic/cas_n.c:41
#2 0xfef823fc in libat_compare_exchange_8 (mptr=0x8049e68, eptr=0x8049e70,
newval=18446744073709551615, smodel=5, fmodel=0) at
/vol/gcc/src/hg/trunk/local/libatomic/cas_n.c:41
#3 0xfef823fc in libat_compare_exchange_8 (mptr=0x8049e68, eptr=0x8049e70,
newval=18446744073709551615, smodel=5, fmodel=0) at
/vol/gcc/src/hg/trunk/local/libatomic/cas_n.c:41
#4 0xfef823fc in libat_compare_exchange_8 (mptr=0x8049e68, eptr=0x8049e70,
newval=18446744073709551615, smodel=5, fmodel=0) at
/vol/gcc/src/hg/trunk/local/libatomic/cas_n.c:41
Seems to be infinite recursion.
Rainer
next reply other threads:[~2012-05-08 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 16:23 ro at gcc dot gnu.org [this message]
2012-05-08 22:56 ` [Bug other/53284] " rth at gcc dot gnu.org
2012-05-09 11:48 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-05-09 18:08 ` rth at gcc dot gnu.org
2012-05-10 9:18 ` ro at gcc dot gnu.org
2012-05-10 9:46 ` ro at gcc dot gnu.org
2012-05-10 12:36 ` dominiq at lps dot ens.fr
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-53284-4@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).