From: Segher Boessenkool <segher@kernel.crashing.org>
To: Bill Schmidt <wschmidt@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org, dje.gcc@gmail.com
Subject: Re: [PATCH 4/4] rs6000: Add ROP tests
Date: Fri, 14 May 2021 14:36:20 -0500 [thread overview]
Message-ID: <20210514193620.GP10366@gate.crashing.org> (raw)
In-Reply-To: <cac348815f75a1a9bc734076e0c6909f225e1987.1620958221.git.wschmidt@linux.ibm.com>
On Thu, May 13, 2021 at 10:34:57PM -0500, Bill Schmidt via Gcc-patches wrote:
> gcc/testsuite/
> * gcc.target/powerpc/rop-1.c: New.
> * gcc.target/powerpc/rop-2.c: New.
> * gcc.target/powerpc/rop-3.c: New.
> * gcc.target/powerpc/rop-4.c: New.
> * gcc.target/powerpc/rop-5.c: New.
Okay for trunk and everything. Thanks!
Segher
next prev parent reply other threads:[~2021-05-14 19:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 3:34 [PATCHv2 0/4] ROP support Bill Schmidt
2021-05-14 3:34 ` [PATCH 1/4] rs6000: Add -mrop-protect and -mprivileged flags Bill Schmidt
2021-05-14 14:18 ` Bill Schmidt
2021-05-14 15:55 ` Segher Boessenkool
2021-05-15 19:06 ` Bill Schmidt
2021-05-14 3:34 ` [PATCH 2/4] rs6000: Emit ROP-mitigation instructions in prologue and epilogue Bill Schmidt
2021-05-14 14:18 ` Bill Schmidt
2021-05-14 18:44 ` Segher Boessenkool
2021-05-14 19:10 ` Bill Schmidt
2021-05-14 3:34 ` [PATCH 3/4] rs6000: Conditionally define __ROP_PROTECT__ Bill Schmidt
2021-05-14 14:18 ` Bill Schmidt
2021-05-14 18:51 ` Segher Boessenkool
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 [this message]
2021-05-14 14:18 ` [PATCHv2 0/4] ROP support Bill Schmidt
-- strict thread matches above, loose matches on Subject: below --
2021-04-26 1:50 [PATCH 0/4] [rs6000] " Bill Schmidt
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
2021-05-12 23:42 ` 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=20210514193620.GP10366@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).