public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/14202] [arm] Thumb __builtin_setjmp not interworking safe
Date: Thu, 19 Feb 2004 15:30:00 -0000 [thread overview]
Message-ID: <20040219153011.5705.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040218230529.14202.drow@gcc.gnu.org>
------- Additional Comments From rearnsha at arm dot com 2004-02-19 15:30 -------
Subject: Re: [arm] Thumb __builtin_setjmp not
interworking safe
>
> Won't that leave bits of GNAT broken? I think it uses __builtin_setjmp
> explicitly.
>
Possibly, but probably no more broken than it already is if it uses that
routine. How can the compiler know to restore registers it doesn't even
know about? The EABI has been carefully constructed to ensure that it
needed care; but builtin_setjmp breaks that assumption.
The ultimate solution will be to convert the ARM port to use the EABI
exception unwinding model, then most of this should be irrelevant from
that point of view.
R.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14202
next prev parent reply other threads:[~2004-02-19 15:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 23:05 [Bug target/14202] New: " drow at gcc dot gnu dot org
2004-02-19 0:15 ` [Bug target/14202] " drow at gcc dot gnu dot org
2004-02-19 1:23 ` pinskia at gcc dot gnu dot org
2004-02-19 12:01 ` rearnsha at gcc dot gnu dot org
2004-02-19 12:02 ` rearnsha at gcc dot gnu dot org
2004-02-19 14:56 ` drow at gcc dot gnu dot org
2004-02-19 15:30 ` Richard Earnshaw
2004-02-19 15:30 ` rearnsha at arm dot com [this message]
2004-02-19 17:51 ` drow at gcc dot gnu dot org
2004-10-11 10:57 ` giovannibajo at libero dot it
2005-07-02 1:31 ` pinskia at gcc dot gnu dot org
[not found] <bug-14202-3264@http.gcc.gnu.org/bugzilla/>
2009-01-02 12:26 ` laurent at guerby dot net
2009-01-05 17:52 ` rearnsha at gcc dot gnu dot org
2009-01-05 18:34 ` drow at gcc dot gnu dot org
2009-04-03 23:27 ` ramana at gcc dot gnu dot org
2009-04-09 11:31 ` ramana at gcc dot gnu dot org
2009-04-17 11:08 ` ramana at gcc dot gnu dot org
2009-10-26 11:37 ` ramana at gcc dot gnu dot org
[not found] <bug-14202-4@http.gcc.gnu.org/bugzilla/>
2012-09-23 22:00 ` pinskia at gcc dot gnu.org
2012-09-24 16:12 ` drow 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=20040219153011.5705.qmail@sources.redhat.com \
--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).