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/106806] [13 regression] gcc.dg/tree-ssa/gen-vect-34.c fails after r13-2333-gca8f4e8af14869 Date: Thu, 03 Nov 2022 06:24:56 +0000 [thread overview] Message-ID: <bug-106806-4-3u2Khxhwi1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106806-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106806 --- Comment #3 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:20d5dca80b82df9b1295359edb44eb08c45c4334 commit r13-3621-g20d5dca80b82df9b1295359edb44eb08c45c4334 Author: Kewen Lin <linkw@linux.ibm.com> Date: Thu Nov 3 01:22:45 2022 -0500 testsuite: Fix gen-vect-34.c with vect_masked_load [PR106806] This is to fix the failure on powerpc as reported in PR106806, the test case requires tree ifcvt pass to perform on that loop, and it relies on masked_load support. The fix is to guard the expected scan with vect_masked_load effective target. As tested on powerpc64{,le}-linux-gnu and aarch64-linux-gnu (cfarm machine), the failures were gone. But on x86_64-redhat-linux (cfarm machine) the result becomes from PASS to N/A. I think it's expected since that machine doesn't support AVX by default so both check_avx_available and vect_masked_load fail, it should work fine on machines with default AVX support, or if we adjust the current check_avx_available with current_compiler_flags. PR testsuite/106806 gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/gen-vect-34.c: Adjust with vect_masked_load effective target.
next prev parent reply other threads:[~2022-11-03 6:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-106806-4@http.gcc.gnu.org/bugzilla/> 2022-09-02 6:35 ` [Bug middle-end/106806] " rguenth at gcc dot gnu.org 2022-09-07 21:39 ` danglin at gcc dot gnu.org 2022-10-19 6:21 ` [Bug testsuite/106806] " rguenth at gcc dot gnu.org 2022-10-28 16:25 ` seurer at gcc dot gnu.org 2022-10-28 16:28 ` seurer at gcc dot gnu.org 2022-11-03 6:24 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-03 6:26 ` 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-106806-4-3u2Khxhwi1@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).