public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52205] SPARC Solaris 2.11 unwind through signal handler fails with -fnon-call-exceptions
Date: Sat, 11 Feb 2012 10:48:00 -0000 [thread overview]
Message-ID: <bug-52205-4-et6Ja0y1Y7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52205-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52205
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot
| |gnu.org
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-02-11 10:47:46 UTC ---
> I see this in both 32-bit and 64-bit mode. If I tweak
> libgcc/config/sparc/sol2-unwind.h so that sparc_is_sighandler sets *nframes to
> 3 rather than 2, then the test passes (I only tried this in 32-bit mode, not in
> 64-bit mode). The cuh_pattern test in sparc_is_sighandler does not match, so
> presumably it needs to be adjusted for Solaris 2.11. However, I'm not sure how
> to properly and safely correct it.
OK, let's at least try, first in 32-bit mode. What code path is taken exactly
in sparc_is_sighandler on Solaris 11?
next prev parent reply other threads:[~2012-02-11 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 23:32 [Bug target/52205] New: " ian at airs dot com
2012-02-10 23:37 ` [Bug target/52205] " pinskia at gcc dot gnu.org
2012-02-11 10:48 ` ebotcazou at gcc dot gnu.org [this message]
2012-02-12 4:13 ` ian at airs dot com
2012-02-12 10:07 ` ebotcazou at gcc dot gnu.org
2012-02-12 15:33 ` ebotcazou at gcc dot gnu.org
2012-02-12 19:53 ` ian at airs dot com
2012-02-12 20:25 ` ebotcazou at gcc dot gnu.org
2012-02-14 18:39 ` [Bug target/52205] unwinding through signal handler fails ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-14 22:05 ` ebotcazou at gcc dot gnu.org
2012-02-15 8:15 ` ebotcazou at gcc dot gnu.org
2012-02-15 8:17 ` ebotcazou at gcc dot gnu.org
2012-02-15 8:22 ` ebotcazou at gcc dot gnu.org
2012-02-16 19:54 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-05-26 13:56 ` ebotcazou at gcc dot gnu.org
2012-05-26 14:12 ` ebotcazou 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-52205-4-et6Ja0y1Y7@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).