From: "H.J. Lu" <hjl.tools@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
Igor Tsimbalist <igor.v.tsimbalist@intel.com>,
Uros Bizjak <ubizjak@gmail.com>
Subject: PING^2 [PATCH] i386: Avoid PLT when shadow stack is enabled directly
Date: Mon, 08 Jan 2018 04:07:00 -0000 [thread overview]
Message-ID: <CAMe9rOrzaKSL+A60tzGeBydrh+sXX2XPPS+bR0j1+-p_J+GzTA@mail.gmail.com> (raw)
On Fri, Dec 8, 2017 at 5:02 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Tue, Oct 24, 2017 at 5:31 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>> PLT should be avoided with shadow stack in 32-bit mode if more than 2
>> parameters are passed in registers since only 2 parameters can be passed
>> in registers for external function calls via PLT with shadow stack
>> enabled.
>>
>> OK for trunk if there is no regressions?
>
> Here is the updated patch.
>
> PING.
PING:
https://gcc.gnu.org/ml/gcc-patches/2017-12/msg00485.html
--
H.J.
next reply other threads:[~2018-01-08 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 4:07 H.J. Lu [this message]
2018-03-17 13:46 H.J. Lu
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=CAMe9rOrzaKSL+A60tzGeBydrh+sXX2XPPS+bR0j1+-p_J+GzTA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=igor.v.tsimbalist@intel.com \
--cc=ubizjak@gmail.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).