public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-3475] rs6000/test: Support vect_long_long effective target Date: Tue, 25 Oct 2022 05:20:14 +0000 (GMT) [thread overview] Message-ID: <20221025052014.39BF63857B81@sourceware.org> (raw) https://gcc.gnu.org/g:321f89e58510dd5df1b3dbe323344b987a7b11c6 commit r13-3475-g321f89e58510dd5df1b3dbe323344b987a7b11c6 Author: Kewen Lin <linkw@linux.ibm.com> Date: Tue Oct 25 00:18:45 2022 -0500 rs6000/test: Support vect_long_long effective target Currently effective target vect_long_long doesn't have power specific check, I think it's an oversight. This is to add the support which checks for has_arch_pwr8, since we set rs6000_vector_unit[V2DImode] as: (TARGET_P8_VECTOR) ? VECTOR_P8_VECTOR : VECTOR_NONE; it means its full support starts from ISA 2.07. Although ISA 2.06 has some instructions like lxvd2x and stxvd2x etc., it's used for testing, checking for ISA 2.07 is more sensitive. gcc/testsuite/ChangeLog: * lib/target-supports.exp (check_effective_target_vect_long_long): Add support for powerpc*-*-*. Diff: --- gcc/testsuite/lib/target-supports.exp | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index 7824a441bca..ccbbee847f7 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -7075,7 +7075,10 @@ proc check_effective_target_vect_long_long { } { || ([istarget mips*-*-*] && [et-is-effective-target mips_msa]) || ([istarget s390*-*-*] - && [check_effective_target_s390_vx]) }}] + && [check_effective_target_s390_vx]) + || ([istarget powerpc*-*-*] + && ![istarget powerpc-*-linux*paired*] + && [check_effective_target_has_arch_pwr8]) }}] }
reply other threads:[~2022-10-25 5:20 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=20221025052014.39BF63857B81@sourceware.org \ --to=linkw@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).