From: Segher Boessenkool <segher@kernel.crashing.org>
To: Bill Schmidt <wschmidt@linux.ibm.com>
Cc: will schmidt <will_schmidt@vnet.ibm.com>,
gcc-patches@gcc.gnu.org, dje.gcc@gmail.com
Subject: Re: [PATCH 4/4] rs6000: Add ROP tests
Date: Wed, 12 May 2021 18:25:11 -0500 [thread overview]
Message-ID: <20210512232511.GD10366@gate.crashing.org> (raw)
In-Reply-To: <32475e36-6494-10ec-3ebb-4c43d7f9cea8@linux.ibm.com>
On Mon, Apr 26, 2021 at 02:27:45PM -0500, Bill Schmidt wrote:
> On 4/26/21 11:04 AM, will schmidt wrote:
> >Does there need to be another test to verify if -mrop-protect is on by
> >default without specifying -mrop-protect? (or is it?) Question on
> >0/4.
>
> It's off by default (see the Init(0) in patch 1/4).
And in general we only need a test for it if the default isn't fixed.
Segher
next prev parent reply other threads:[~2021-05-12 23:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 1:50 [PATCH 0/4] [rs6000] ROP support Bill Schmidt
2021-04-26 1:50 ` [PATCH 1/4] rs6000: Add -mrop-protect and -mprivileged flags Bill Schmidt
2021-04-26 16:02 ` will schmidt
2021-05-12 20:40 ` Segher Boessenkool
2021-05-12 20:26 ` Segher Boessenkool
2021-04-26 1:50 ` [PATCH 2/4] rs6000: Emit ROP-protect instructions in prologue and epilogue Bill Schmidt
2021-04-26 16:03 ` will schmidt
2021-05-12 23:09 ` Segher Boessenkool
2021-04-26 1:50 ` [PATCH 3/4] rs6000: Conditionally define __ROP_PROTECT__ Bill Schmidt
2021-04-26 16:03 ` will schmidt
2021-05-12 23:19 ` Segher Boessenkool
2021-05-12 23:20 ` Segher Boessenkool
2021-04-26 1:50 ` [PATCH 4/4] rs6000: Add ROP tests Bill Schmidt
2021-04-26 16:04 ` will schmidt
2021-04-26 19:27 ` Bill Schmidt
2021-05-12 23:25 ` Segher Boessenkool [this message]
2021-05-12 23:42 ` Segher Boessenkool
2021-04-26 16:01 ` [PATCH 0/4] [rs6000] ROP support will schmidt
2021-04-26 16:33 ` Bill Schmidt
2021-05-11 15:56 ` Bill Schmidt
2021-05-14 3:34 [PATCHv2 0/4] " Bill Schmidt
2021-05-14 3:34 ` [PATCH 4/4] rs6000: Add ROP tests Bill Schmidt
2021-05-14 14:18 ` Bill Schmidt
2021-05-14 19:36 ` Segher Boessenkool
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=20210512232511.GD10366@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=will_schmidt@vnet.ibm.com \
--cc=wschmidt@linux.ibm.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).