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 target/60290] New: 32-bit g++.dg/cilk-plus/CK/catch_exc.cc FAILs on Solaris/x86
Date: Thu, 20 Feb 2014 12:30:00 -0000 [thread overview]
Message-ID: <bug-60290-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60290
Bug ID: 60290
Summary: 32-bit g++.dg/cilk-plus/CK/catch_exc.cc FAILs on
Solaris/x86
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: bviyer at gcc dot gnu.org
Host: i386-pc-solaris2.1[01]
Target: i386-pc-solaris2.1[01]
Build: i386-pc-solaris2.1[01]
The 32-bit g++.dg/cilk-plus/CK/catch_exc.cc execution test FAILs on Solaris 10
and 11/x86:
FAIL: g++.dg/cilk-plus/CK/catch_exc.cc -O1 -fcilkplus execution test
FAIL: g++.dg/cilk-plus/CK/catch_exc.cc -O3 -fcilkplus execution test
FAIL: g++.dg/cilk-plus/CK/catch_exc.cc -g -fcilkplus execution test
FAIL: g++.dg/cilk-plus/CK/catch_exc.cc -g -O2 -fcilkplus execution test
while the 64-bit test is fine.
For the -g case, I see
Program received signal SIGABRT, Aborted.
[Switching to Thread 1 (LWP 1)]
0xfe4cab67 in __lwp_sigqueue () from /lib/libc.so.1
(gdb) where
#0 0xfe4cab67 in __lwp_sigqueue () from /lib/libc.so.1
#1 0xfe4c41c0 in thr_kill () from /lib/libc.so.1
#2 0xfe47263d in raise () from /lib/libc.so.1
#3 0xfe448d7d in abort () from /lib/libc.so.1
#4 0xfe5a4bd7 in _Unwind_Resume (exc=0x80a2da0)
at /vol/gcc/src/hg/trunk/local/libgcc/unwind.inc:234
#5 0xfe761b65 in __cilkrts_gcc_rethrow (sf=0xfeffe3f0)
at /vol/gcc/src/hg/trunk/local/libcilkrts/runtime/except-gcc.cpp:589
#6 0xfe75d21a in __cilkrts_rethrow (sf=0xfeffe3f0)
at /vol/gcc/src/hg/trunk/local/libcilkrts/runtime/cilk-abi.c:548
#7 0x08051436 in my_test ()
at
/vol/gcc/src/hg/trunk/local/gcc/testsuite/g++.dg/cilk-plus/CK/catch_exc.cc:37
#8 0x08051660 in main ()
at
/vol/gcc/src/hg/trunk/local/gcc/testsuite/g++.dg/cilk-plus/CK/catch_exc.cc:62
Rainer
next reply other threads:[~2014-02-20 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 12:30 ro at gcc dot gnu.org [this message]
2014-02-20 12:30 ` [Bug target/60290] " ro at gcc dot gnu.org
2014-02-20 13:16 ` jakub at gcc dot gnu.org
2014-04-22 11:36 ` jakub at gcc dot gnu.org
2014-07-16 13:29 ` jakub at gcc dot gnu.org
2014-10-30 10:38 ` jakub at gcc dot gnu.org
2015-06-26 20:16 ` jakub at gcc dot gnu.org
2015-06-26 20:38 ` jakub at gcc dot gnu.org
2015-06-26 21:28 ` 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-60290-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).