From: Segher Boessenkool <segher@kernel.crashing.org>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc@gcc.gnu.org, Peter Bergner <bergner@vnet.ibm.com>,
Jeff Law <law@redhat.com>,
Vladimir N Makarov <vmakarov@redhat.com>,
Pat Haugen <pthaugen@linux.vnet.ibm.com>
Subject: Re: Why does IRA force all pseudos live across a setjmp call to be spilled?
Date: Mon, 05 Mar 2018 15:33:00 -0000 [thread overview]
Message-ID: <20180305153325.GQ21977@gate.crashing.org> (raw)
In-Reply-To: <1798327.obcmBFoBij@polaris>
On Mon, Mar 05, 2018 at 08:01:14AM +0100, Eric Botcazou wrote:
> > C11 says in 7.13.2.1/2
> > "The longjmp function restores the environment saved by the most recent
> > invocation of the setjmp macro in the same invocation of the program with
> > the corresponding jmp_buf argument."
> > where "environment" is not really defined, but it includes all information
> > a program will need to return to its caller (so it has to restore the
> > non-volatile registers, set stack pointers correctly, that kind of thing).
>
> Apparently the authors of the SPARC psABI thought that the last part of your
> sentence is an interpolation and that the (historical) requirements were vague
> enough to allow their interpretation, IOW that the compiler can do the work.
Maybe we should have a target hook that says setjmp/longjmp are
implemented by simple function calls (or as-if by function calls), so
as not to penalize everyone who has an, erm, more conservative ABI?
Segher
next prev parent reply other threads:[~2018-03-05 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 19:45 Peter Bergner
2018-03-02 19:55 ` Alexander Monakov
2018-03-02 21:26 ` Jeff Law
2018-03-03 3:28 ` Peter Bergner
2018-03-03 16:29 ` Jeff Law
2018-03-03 23:47 ` Peter Bergner
2018-03-04 0:30 ` Peter Bergner
2018-03-04 8:57 ` Richard Biener
2018-03-04 9:11 ` Andreas Schwab
2018-03-05 2:12 ` Jeff Law
2018-03-04 13:57 ` Eric Botcazou
2018-03-04 16:40 ` Peter Bergner
2018-03-04 17:39 ` Andreas Schwab
2018-03-05 0:16 ` Segher Boessenkool
2018-03-05 7:01 ` Eric Botcazou
2018-03-05 7:09 ` Eric Botcazou
2018-03-05 15:33 ` Segher Boessenkool [this message]
2018-03-05 16:18 ` Eric Botcazou
2018-03-06 16:20 ` Peter Bergner
2018-03-03 3:21 ` Vladimir Makarov
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=20180305153325.GQ21977@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@vnet.ibm.com \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=pthaugen@linux.vnet.ibm.com \
--cc=vmakarov@redhat.com \
/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).