public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/27937] [4.2 Regression] Ada bootstrap failure on Solaris 10/x86
Date: Mon, 12 Jun 2006 18:53:00 -0000 [thread overview]
Message-ID: <20060612181130.2394.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27937-81@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from ebotcazou at gcc dot gnu dot org 2006-06-12 18:11 -------
> Ok, I see. Thanks for the explanation. Any reason this is done this way?
> Solaris/SPARC doesn't use this, nor does Linux/x86, so it seems like both
> the Solaris and x86 parts of the code are there.
Short answer: seamless support for synchronous signals.
Long answer: we want to be able to turn synchronous signals into regular Ada
exceptions. This means unwinding through signal handler frames (easy) and
unwinding through kernel frames (tricky). With SJLJ exceptions, the latter
turns out to be transparent; but with DWARF-2 EH exceptions, you need specific
support code under the form of MD_FALLBACK_FRAME_STATE_FOR macros, defined in
the *-unwind.h files. The FSF tree contains some M_F_F_S_F macros, we have
a few more, in particular for SPARC/Solaris but not for x86/Solaris. We should
already have contributed them, but there is a discrepancy between Java and Ada
in this domain that should be sorted out first.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27937
next prev parent reply other threads:[~2006-06-12 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 18:23 [Bug ada/27937] New: " gcc-bugzilla at gcc dot gnu dot org
2006-06-09 7:25 ` [Bug ada/27937] " pinskia at gcc dot gnu dot org
2006-06-09 9:34 ` ebotcazou at gcc dot gnu dot org
2006-06-09 16:08 ` ro at techfak dot uni-bielefeld dot de
2006-06-11 15:45 ` ebotcazou at gcc dot gnu dot org
2006-06-12 18:04 ` ro at techfak dot uni-bielefeld dot de
2006-06-12 18:53 ` ebotcazou at gcc dot gnu dot org [this message]
2006-06-21 18:02 ` ro at techfak dot uni-bielefeld dot de
2006-06-21 18:14 ` ebotcazou at gcc dot gnu dot org
2006-06-21 18:32 ` ro at techfak dot uni-bielefeld dot de
2006-06-25 11:07 ` [Bug tree-optimization/27937] " rguenth at gcc dot gnu dot org
2006-07-05 17:57 ` mmitchel at gcc dot gnu dot org
2006-07-24 8:33 ` rguenth at gcc dot gnu dot org
2006-07-28 16:03 ` ro at techfak dot uni-bielefeld dot de
2006-07-28 16:22 ` pinskia at gcc dot gnu dot org
2006-08-04 21:37 ` ebotcazou at gcc dot gnu dot 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=20060612181130.2394.qmail@sourceware.org \
--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).