From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com, Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH 1/3] rs6000: Add effective target has_arch_ppc64
Date: Thu, 21 Apr 2022 21:28:11 +0000 [thread overview]
Message-ID: <11a99c2b7440227646877c36e150073342026337.1650575998.git.segher@kernel.crashing.org> (raw)
In-Reply-To: <cover.1650575998.git.segher@kernel.crashing.org>
In-Reply-To: <cover.1650575998.git.segher@kernel.crashing.org>
This is true if we have -mpowerpc64.
2022-04-21 Segher Boessenkool <segher@kernel.crashing.org>
gcc/testsuite/
* lib/target-supports.exp (check_effective_target_has_arch_ppc64): New.
---
gcc/testsuite/lib/target-supports.exp | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 90b900956822..8bdb4a845f54 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -6378,6 +6378,16 @@ proc check_effective_target_has_arch_pwr10 { } {
}]
}
+proc check_effective_target_has_arch_ppc64 { } {
+ return [check_no_compiler_messages arch_ppc64 assembly {
+ #ifndef _ARCH_PPC64
+ #error does not have ppc64 support.
+ #else
+ /* "has ppc64 support" */
+ #endif
+ }]
+}
+
# Return 1 if this is a PowerPC target supporting -mcpu=power10.
# Limit this to 64-bit linux systems for now until other targets support
# power10.
--
1.8.3.1
next prev parent reply other threads:[~2022-04-21 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 21:28 [PATCH 0/3] rs6000: Disparage lfiwzx and similar Segher Boessenkool
2022-04-21 21:28 ` Segher Boessenkool [this message]
2022-04-21 21:28 ` [PATCH 2/3] " Segher Boessenkool
2022-04-21 21:28 ` [PATCH 3/3] rs6000/testsuite: xfail bswap-brw.c 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=11a99c2b7440227646877c36e150073342026337.1650575998.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@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: 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).