From: Roland McGrath <roland@hack.frob.com>
To: Will Newton <will.newton@linaro.org>
Cc: libc-ports@sourceware.org
Subject: Re: ARM per-thread stack protector
Date: Mon, 22 Jul 2013 22:01:00 -0000 [thread overview]
Message-ID: <20130722220100.A1AD62C06F@topped-with-meat.com> (raw)
In-Reply-To: Will Newton's message of Monday, 22 July 2013 10:15:13 +0100 <CANu=DmhQXD2NO4a2ACned-s08m6jzjJaQ2vPO4FppdDejsjiBg@mail.gmail.com>
> Thanks for the clarification. So the two methods are functionally identical?
Yes. Where you keep the value is just a matter of optimal implementation
convenience for the particular machine.
> >From what I understand then all that is missing on ARM from that list
> is pointer mangling support?
I have no new information.
prev parent reply other threads:[~2013-07-22 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 16:34 Will Newton
2013-07-19 21:41 ` Roland McGrath
2013-07-22 9:15 ` Will Newton
2013-07-22 22:01 ` Roland McGrath [this message]
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=20130722220100.A1AD62C06F@topped-with-meat.com \
--to=roland@hack.frob.com \
--cc=libc-ports@sourceware.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).