public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Will Newton <will.newton@linaro.org>
To: Roland McGrath <roland@hack.frob.com>
Cc: "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 12:38:00 -0000	[thread overview]
Message-ID: <CANu=DmjAG8zxFOwWeJZuEFLXEcSTROVZsR1oRZc9qx=Zcn9T-w@mail.gmail.com> (raw)
In-Reply-To: <20140206221127.6E28974443@topped-with-meat.com>

On 6 February 2014 22:11, Roland McGrath <roland@hack.frob.com> wrote:
> Can you clarify why you want to change the jmp_buf layout?
> I don't see why any change you might want to make would necessitate that.

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?

-- 
Will Newton
Toolchain Working Group, Linaro

  reply	other threads:[~2014-02-07 12:38 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 [this message]
2014-02-07 14:16     ` Andreas Schwab
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='CANu=DmjAG8zxFOwWeJZuEFLXEcSTROVZsR1oRZc9qx=Zcn9T-w@mail.gmail.com' \
    --to=will.newton@linaro.org \
    --cc=libc-ports@sourceware.org \
    --cc=patches@linaro.org \
    --cc=roland@hack.frob.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).