public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/108729] gcc.target/powerpc/bfp/scalar-test-data-class-12.c fails on power 9 BE Date: Wed, 08 Mar 2023 06:59:57 +0000 [thread overview] Message-ID: <bug-108729-4-GyrTIHJo1j@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108729-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108729 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:bab3b6a9c3bde32903815826f96abc18e62bff6e commit r13-6542-gbab3b6a9c3bde32903815826f96abc18e62bff6e Author: Kewen Lin <linkw@linux.ibm.com> Date: Wed Mar 8 00:56:32 2023 -0600 testsuite: Adjust two bfp test cases with has_arch_ppc64 [PR108729] Two test cases scalar-test-data-class-12.c and vec-test-data-class-9.c fail on Power9 BE testing at -m32, they adopts a built-in function scalar_insert_exp which requires powerpc64 support. This patch is to make them to check has_arch_ppc64 effective target requirement. PR testsuite/108729 gcc/testsuite/ChangeLog: * gcc.target/powerpc/bfp/scalar-test-data-class-12.c: Adjust with has_arch_ppc64 effective target. * gcc.target/powerpc/bfp/vec-test-data-class-9.c: Likewise.
next prev parent reply other threads:[~2023-03-08 6:59 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 21:17 [Bug target/108729] New: " seurer at gcc dot gnu.org 2023-02-14 11:20 ` [Bug target/108729] " linkw at gcc dot gnu.org 2023-02-14 11:35 ` linkw at gcc dot gnu.org 2023-02-14 11:46 ` linkw at gcc dot gnu.org 2023-03-01 6:04 ` [Bug testsuite/108729] " linkw at gcc dot gnu.org 2023-03-08 6:59 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-08 7:51 ` linkw at gcc dot gnu.org 2023-03-08 7:55 ` linkw at gcc dot gnu.org
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=bug-108729-4-GyrTIHJo1j@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).