From: "Jonathan S. Shapiro" <shap@eros-os.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Will Newton <will.newton@linaro.org>,
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 15:45:00 -0000 [thread overview]
Message-ID: <CAAP=3QNj5eYe6EaRDpGURw+e0nho5cZ-orh97vREp3rc=ATy7Q@mail.gmail.com> (raw)
In-Reply-To: <8761orknyz.fsf@igel.home>
On Fri, Feb 7, 2014 at 6:16 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> According to ports/sysdeps/arm/bits/setjmp.h the layout of jmp_buf is
> part of the ABI.
Yes. The layout of jmp_buf is part of the ABI. And not just the libc ABI,
but for some platforms it's part of the platform standard (e.g. SVID
specifies it). In consequence, changing the structure layout isn't an
option in either the current libc release or any foreseeable future libc
release. The patch point needs to be reworked so as to operate given the
current structure layout.
On the bright side, reworking the code to fit the current layout means that
(a) this can be integrated sooner, and (b) we don't have to accept a small
regression in GDB functionality in order to implement encrypted pointers.
Jonathan
next prev parent reply other threads:[~2014-02-07 15:45 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
2014-02-07 15:45 ` Jonathan S. Shapiro [this message]
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='CAAP=3QNj5eYe6EaRDpGURw+e0nho5cZ-orh97vREp3rc=ATy7Q@mail.gmail.com' \
--to=shap@eros-os.org \
--cc=libc-ports@sourceware.org \
--cc=patches@linaro.org \
--cc=roland@hack.frob.com \
--cc=schwab@linux-m68k.org \
--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).