From: Andreas Schwab <schwab@linux-m68k.org>
To: Will Newton <will.newton@linaro.org>
Cc: Roland McGrath <roland@hack.frob.com>,
"libc-ports\@sourceware.org" <libc-ports@sourceware.org>,
Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH v2] ARM: Add SystemTap probes to longjmp and setjmp.
Date: Fri, 07 Feb 2014 14:16:00 -0000 [thread overview]
Message-ID: <8761orknyz.fsf@igel.home> (raw)
In-Reply-To: <CANu=DmjAG8zxFOwWeJZuEFLXEcSTROVZsR1oRZc9qx=Zcn9T-w@mail.gmail.com> (Will Newton's message of "Fri, 7 Feb 2014 12:38:49 +0000")
Will Newton <will.newton@linaro.org> writes:
> In order to have the correct registers live I need to free up a temp
> register which involves loading lr and sp earlier than the
> call-preserved register set. I could do this by offsetting into the
> jmpbuf but it seems more natural just to move lr and sp to the front
> of the jmp_buf and load registers in ascending order. As far as I am
> aware the layout of jmp_buf is completely opaque so I don't see why
> this would cause any problems?
According to ports/sysdeps/arm/bits/setjmp.h the layout of jmp_buf is
part of the ABI.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2014-02-07 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 9:56 Will Newton
2014-02-06 16:26 ` Carlos O'Donell
2014-02-06 16:41 ` Joseph S. Myers
2014-02-06 16:48 ` Will Newton
2014-02-06 16:54 ` Carlos O'Donell
2014-02-06 22:11 ` Roland McGrath
2014-02-07 12:38 ` Will Newton
2014-02-07 14:16 ` Andreas Schwab [this message]
2014-02-07 15:45 ` Jonathan S. Shapiro
2014-02-07 17:04 ` Joseph S. Myers
[not found] ` <CAAP=3QP6_TvyFdpmO9Or5E2=NFCdcUVrCGBHT3rMozRXLT4mmw@mail.gmail.com>
2014-02-10 8:54 ` Will Newton
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=8761orknyz.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=libc-ports@sourceware.org \
--cc=patches@linaro.org \
--cc=roland@hack.frob.com \
--cc=will.newton@linaro.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).