From: Bobby Bingham <koorogi@koorogi.info>
To: musl@lists.openwall.com
Subject: Re: possible bug in setjmp implementation for ppc64
Date: Wed, 2 Aug 2017 19:19:44 -0500 [thread overview]
Message-ID: <20170803001944.GC5455@dora.lan> (raw)
In-Reply-To: <20170802144612.GI1627@brightrain.aerifal.cx>
On Wed, Aug 02, 2017 at 10:46:12AM -0400, Rich Felker wrote:
> On Wed, Aug 02, 2017 at 08:38:25AM -0500, Bobby Bingham wrote:
> Whether the call to longjmp/siglongjmp was local or not is irrelevant.
> It's only whether the original call to setjmp/sigsetjmp was local or
> not that's relevant. And in either case I'm pretty sure it suffices to
I think I was treating whether longjmp is called locally as a proxy for
whether setjmp was called locally. But of course that doesn't work.
I think we're on the same page now.
> restore the saved value to both *(r1+24) and r2. Per the ABI, *(r1+24)
> can't be used for any purpose except saving the TOC, so upon return
> from setjmp, the caller's only options are to treat the value at
> *(r1+24) as indeterminate or assume it contains the TOC pointer.
> Likewise for r2, if the call was non-local, r2 is call-clobbered so it
> doesn't matter what it contains after return, and if the call was
> local, r2 is expected to contain the caller's TOC pointer.
>
> Rich
next prev parent reply other threads:[~2017-08-03 0:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 20:06 felix.winkelmann
2017-07-31 20:30 ` Rich Felker
2017-08-01 5:10 ` Bobby Bingham
2017-08-01 5:28 ` Alexander Monakov
2017-08-01 22:45 ` Rich Felker
2017-08-01 23:07 ` Rich Felker
2017-08-02 0:28 ` Bobby Bingham
2017-08-02 3:55 ` Rich Felker
2017-08-02 4:31 ` Bobby Bingham
2017-08-02 4:58 ` Rich Felker
2017-08-02 13:38 ` Bobby Bingham
2017-08-02 14:46 ` Rich Felker
2017-08-03 0:19 ` Bobby Bingham [this message]
2017-08-01 15:33 ` David Edelsohn
2017-08-02 23:00 ` Alexander Monakov
2017-08-02 23:02 ` Rich Felker
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=20170803001944.GC5455@dora.lan \
--to=koorogi@koorogi.info \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).