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] e500 exception unwinding under "-Os" causes SIGSEGV Date: Thu, 03 Nov 2011 16:49:00 -0000 [thread overview] Message-ID: <bug-50906-4-2jBGfUWKRu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50906-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50906 --- Comment #11 from Kyle Moffett <Kyle.D.Moffett at boeing dot com> 2011-11-03 16:48:43 UTC --- Ok, I'm running a "bootstrap-lean" + "make check" by way of a full Debian GCC package build with this patch added. The first build will just do C/C++/ObjC/ObjC++/Fortran; if that works out OK I will also do a Java build in a little while. I applied a 1-line patch to make the package build set "BOOT_CFLAGS := -g -O2" as you requested, so hopefully any fallout will be obvious during the GCC build itself. There are 2 other patches I have applied on top of the Debian GCC 4.6.2-3 package to fix the SPE build: * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647288 * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647324 The libffi one applies on top of these patches already in the Debian package: * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644338 Based on the speed of this board and the fact that I am using it for other testing as well, I expect to have the test results in roughly 6-8 hours. Cheers, Kyle Moffett -- Curious about my work on the Debian powerpcspe port? I'm keeping a blog here: http://pureperl.blogspot.com/
next prev parent reply other threads:[~2011-11-03 16:49 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-28 20:29 [Bug target/50906] New: " Kyle.D.Moffett at boeing dot com 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 [this message] 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-2jBGfUWKRu@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: linkBe 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).