From: Alan Modra <amodra@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [RS6000] PR96493, powerpc local call linkage failure
Date: Tue, 11 Aug 2020 18:38:53 +0930 [thread overview]
Message-ID: <20200811090853.GT15695@bubble.grove.modra.org> (raw)
In-Reply-To: <20200807032808.GI15695@bubble.grove.modra.org>
This fixes a fail when power10 isn't supported by binutils, and
ensures the test isn't run without power10 hardware or simulation on
the off chance that power10 insns are emitted in the future for this
testcase. Bootstrapped etc. OK?
PR target/96525
* testsuite/gcc.target/powerpc/pr96493.c: Make it a link test
when no power10_hw. Require power10_ok.
diff --git a/gcc/testsuite/gcc.target/powerpc/pr96493.c b/gcc/testsuite/gcc.target/powerpc/pr96493.c
index f0de0818813..1e5d43f199d 100644
--- a/gcc/testsuite/gcc.target/powerpc/pr96493.c
+++ b/gcc/testsuite/gcc.target/powerpc/pr96493.c
@@ -1,6 +1,8 @@
-/* { dg-do run } */
+/* { dg-do run { target { power10_hw } } } */
+/* { dg-do link { target { ! power10_hw } } } */
/* { dg-options "-mdejagnu-cpu=power8 -O2" } */
/* { dg-require-effective-target powerpc_elfv2 } */
+/* { dg-require-effective-target power10_ok } */
/* Test local calls between pcrel and non-pcrel code.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2020-08-11 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 13:28 Alan Modra
2020-08-06 22:34 ` Segher Boessenkool
2020-08-07 3:28 ` Alan Modra
2020-08-07 14:48 ` Segher Boessenkool
2020-08-11 9:08 ` Alan Modra [this message]
2020-08-11 16:35 ` Segher Boessenkool
2020-08-11 17:36 ` Peter Bergner
2020-08-11 18:30 ` Segher Boessenkool
2020-08-12 4:02 ` Alan Modra
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=20200811090853.GT15695@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).