public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107855] New: gcc.dg/vect/vect-ifcvt-18.c FAILs
Date: Thu, 24 Nov 2022 09:22:53 +0000 [thread overview]
Message-ID: <bug-107855-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107855
Bug ID: 107855
Summary: gcc.dg/vect/vect-ifcvt-18.c FAILs
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: lingling.kong7 at gmail dot com
Target Milestone: ---
Target: i386-pc-solaris2.12, x86_64-pc-linux-gnu
Since it was introduced, the new gcc.dg/vect/vect-ifcvt-18.c test FAILs on
Solaris/x86:
* 32-bit:
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"
* 64-bit:
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 scan-tree-dump vect "vectorized 3 loops"
There are also several gcc-testresults reports for Linux/x86_64.
The 32-bit execution test hits abort in l.34 (nothing useful to be learned
from gdb: res? all optimized out. I'm also including the 32-bit dump.
next reply other threads:[~2022-11-24 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 9:22 ro at gcc dot gnu.org [this message]
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
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@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).