public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Kyle.D.Moffett at boeing dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50906] New: e500 exception unwinding under "-Os" causes SIGSEGV
Date: Fri, 28 Oct 2011 20:29:00 -0000 [thread overview]
Message-ID: <bug-50906-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50906
Bug #: 50906
Summary: e500 exception unwinding under "-Os" causes SIGSEGV
Classification: Unclassified
Product: gcc
Version: 4.6.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: Kyle.D.Moffett@boeing.com
Created attachment 25649
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25649
Test case, part 1
The libffi test-suite is failing on an e500v2 build of GCC 4.6.1 with a
segmentation fault in libgcc (called from "throw()" in the "unwindtest.cc"
file).
The target GCC configure options:
--build/--host/--target=powerpc-linux-gnuspe
--with-cpu=8548
--enable-e500_double
--with-long-double-128
I have extracted it to the attached minimal test-case, compiled as follows:
$ g++ -Wall -Wextra -Werror -ggdb3 -Os -c unwindtest.cc -o unwindtest.o
$ g++ -Wall -Wextra -Werror -ggdb3 -Os -c unwindtestfunc.cc -o
unwindtestfunc.o
$ g++ -ggdb3 -Os -o unwindtest unwindtest.o unwindtestfunc.o
The test fails if "unwindtestfunc.cc" is built with "-Os", but not if it is
built with "-O2". The compile options for unwindtest.cc have no effect on the
success or failure of the test.
Cheers,
Kyle Moffett
--
Curious about my work on the Debian powerpcspe port?
I'm keeping a blog here: http://pureperl.blogspot.com/
next reply other threads:[~2011-10-28 20:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 20:29 Kyle.D.Moffett at boeing dot com [this message]
2011-10-28 20:30 ` [Bug target/50906] " Kyle.D.Moffett at boeing dot com
2011-10-28 20:32 ` Kyle.D.Moffett at boeing dot com
2011-10-28 20:32 ` Kyle.D.Moffett at boeing dot com
2011-11-01 23:44 ` amodra at gmail dot com
2011-11-02 0:06 ` amodra at gmail dot com
2011-11-02 18:24 ` Kyle.D.Moffett at boeing dot com
2011-11-03 4:18 ` amodra at gmail dot com
2011-11-03 12:54 ` amodra at gmail dot com
2011-11-03 12:56 ` amodra at gmail dot com
2011-11-03 12:59 ` amodra at gmail dot com
2011-11-03 16:49 ` Kyle.D.Moffett at boeing dot com
2011-11-04 10:01 ` amodra at gmail dot com
2011-11-04 10:02 ` amodra at gmail dot com
2011-11-04 21:21 ` Kyle.D.Moffett at boeing dot com
2011-11-08 19:28 ` Kyle.D.Moffett at boeing dot com
2011-11-11 10:15 ` dvdkhlng at gmx dot de
2011-11-22 18:57 ` Kyle.D.Moffett at boeing dot com
2011-11-28 20:12 ` Kyle.D.Moffett at boeing dot com
2011-12-06 3:42 ` amodra at gcc dot gnu.org
2011-12-06 3:48 ` amodra at gcc dot gnu.org
2011-12-06 3:49 ` amodra at gmail dot com
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-50906-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).