public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114072] gcc.dg/vect/vect-pr111779.c FAILs Date: Wed, 22 May 2024 12:14:34 +0000 [thread overview] Message-ID: <bug-114072-4-VIFebx7MrS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114072-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114072 --- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> --- [...] >> I think the best we can do then is >> >> /* { dg-skip-if "PR tree-optimization/114072" { be && { ! vect_shift_char } } } >> */ >> >> Lets the test become UNSUPPORTED on 32 and 64-bit SPARC, but still PASS >> as before on 32 and 64-bit x86. > > Can we instead guard the scan-tree-dump? This way the correctness > execute part still is exercised? Sure, even if the result is somewhat hard to read with all those levels of braces: /* { dg-final { scan-tree-dump "LOOP VECTORIZED" "vect" { target { vect_int && { le || { be && vect_shift_char } } } } } } */ This way, all of compile, execute, and scan are run on x86, while on sparc it's only compile, execute.
next prev parent reply other threads:[~2024-05-22 12:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-23 9:58 [Bug tree-optimization/114072] New: " ro at gcc dot gnu.org 2024-05-22 9:16 ` [Bug tree-optimization/114072] " ro at gcc dot gnu.org 2024-05-22 9:36 ` rguenth at gcc dot gnu.org 2024-05-22 11:30 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-22 12:01 ` rguenther at suse dot de 2024-05-22 12:14 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2024-05-22 12:30 ` rguenther at suse dot de 2024-05-23 7:54 ` cvs-commit at gcc dot gnu.org 2024-05-23 7:57 ` ro 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-114072-4-VIFebx7MrS@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).