public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: William Schmidt <wschmidt@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-8496] PR100750: Require ELFv2 ABI for ROP test Date: Tue, 1 Jun 2021 20:47:54 +0000 (GMT) [thread overview] Message-ID: <20210601204754.6A3B03855035@sourceware.org> (raw) https://gcc.gnu.org/g:3d75b5cd9a362172838825c7083a3afa2403735a commit r11-8496-g3d75b5cd9a362172838825c7083a3afa2403735a Author: Bill Schmidt <wschmidt@linux.ibm.com> Date: Tue Jun 1 15:47:22 2021 -0500 PR100750: Require ELFv2 ABI for ROP test 2021-06-01 Bill Schmidt <wschmidt@linux.ibm.com> gcc/testsuite/ PR testsuite/100750 * gcc.target/powerpc/rop-5.c: Require ELFv2 ABI. Diff: --- gcc/testsuite/gcc.target/powerpc/rop-5.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/gcc.target/powerpc/rop-5.c b/gcc/testsuite/gcc.target/powerpc/rop-5.c index cf04ea90eeb..f2594df8a44 100644 --- a/gcc/testsuite/gcc.target/powerpc/rop-5.c +++ b/gcc/testsuite/gcc.target/powerpc/rop-5.c @@ -1,4 +1,5 @@ /* { dg-do compile } */ +/* { dg-require-effective-target powerpc_elfv2 } */ /* { dg-options "-O2 -mdejagnu-cpu=power10 -mrop-protect" } */ /* Verify that __ROP_PROTECT__ is predefined for -mrop-protect. */
reply other threads:[~2021-06-01 20:47 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210601204754.6A3B03855035@sourceware.org \ --to=wschmidt@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).