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/107855] gcc.dg/vect/vect-ifcvt-18.c FAILs
Date: Mon, 26 Feb 2024 13:56:56 +0000 [thread overview]
Message-ID: <bug-107855-4-H9tAPC3hp5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107855-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107855
--- Comment #8 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #6 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
> Hmm, the test contains
>
> "/* { dg-additional-options "-Ofast -mavx" { target avx_runtime } } */"
>
> So it passes on AVX capable native builds, but fails otherwise.
I can reproduce things in a VM now: when it doesn't have avx support,
the test is compiled with -msse2 only and FAILs both for the dump and
execution:
FAIL: gcc.dg/vect/vect-ifcvt-18.c -flto -ffat-lto-objects scan-tree-dump vect
"vectorized 3 loops"
FAIL: gcc.dg/vect/vect-ifcvt-18.c -flto -ffat-lto-objects execution test
FAIL: gcc.dg/vect/vect-ifcvt-18.c execution test
FAIL: gcc.dg/vect/vect-ifcvt-18.c scan-tree-dump vect "vectorized 3 loops"
The test aborts here:
Thread 2 received signal SIGABRT, Aborted.
#0 0xfe26e385 in __lwp_sigqueue () from /lib/libc.so.1
#1 0xfe2660ef in thr_kill () from /lib/libc.so.1
#2 0xfe19db82 in raise () from /lib/libc.so.1
#3 0xfe16b1f4 in abort () from /lib/libc.so.1
#4 0x08050d58 in main ()
at
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-ifcvt-18.c:34
and the dump shows
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-ifcvt-18.c:28:17:
note: === analyze_loop_nest ===
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-ifcvt-18.c:28:17:
note: === vect_analyze_loop_form ===
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-ifcvt-18.c:28:17:
note: using as main loop exit: 13 -> 14 [AUX: 0]
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-ifcvt-18.c:28:17:
missed: not vectorized: unsupported control flow in loop.
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-ifcvt-18.c:28:17:
missed: bad loop form.
/vol/gcc/src/hg/master/local/gcc/testsuite/gcc.dg/vect/vect-ifcvt-18.c:28:17:
missed: couldn't vectorize loop
When I add avx support to the VM, the test PASSes.
It seems the test is missing some requirement here.
next prev parent reply other threads:[~2024-02-26 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 9:22 [Bug tree-optimization/107855] New: " ro at gcc dot gnu.org
2022-11-24 9:24 ` [Bug tree-optimization/107855] " ro at gcc dot gnu.org
2022-11-24 9:24 ` ro at gcc dot gnu.org
2022-11-24 10:52 ` rguenth at gcc dot gnu.org
2022-11-24 10:59 ` ro at gcc dot gnu.org
2022-11-24 11:00 ` ro at gcc dot gnu.org
2023-04-26 6:57 ` rguenth at gcc dot gnu.org
2023-05-13 7:03 ` xry111 at gcc dot gnu.org
2023-07-27 9:24 ` rguenth at gcc dot gnu.org
2024-02-26 13:56 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2024-05-21 9:13 ` jakub 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-107855-4-H9tAPC3hp5@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: 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).