public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thiago.bauermann at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/111125] New: tree-ssa.exp and vect.exp failures after commit 99b5921bfc8f
Date: Thu, 24 Aug 2023 02:05:53 +0000 [thread overview]
Message-ID: <bug-111125-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111125
Bug ID: 111125
Summary: tree-ssa.exp and vect.exp failures after commit
99b5921bfc8f
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: thiago.bauermann at linaro dot org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
Target: aarch64
Created attachment 55784
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55784&action=edit
gcc.log from commit 829c0c06fe7b
Our CI detected that commit 99b5921bfc8f "Handle TYPE_OVERFLOW_UNDEFINED
vectorized BB reductions" introduced these testsuite failures on aarch64-linux:
=== gcc tests ===
Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ...
FAIL: gcc.dg/tree-ssa/slsr-11.c scan-tree-dump-times optimized " \\* " 1
Running gcc:gcc.dg/vect/vect.exp ...
FAIL: gcc.dg/vect/bb-slp-29.c -flto -ffat-lto-objects scan-tree-dump-times
slp1 "optimized: basic block" 1
FAIL: gcc.dg/vect/bb-slp-29.c scan-tree-dump-times slp1 "optimized: basic
block" 1
FAIL: gcc.dg/vect/pr53773.c -flto -ffat-lto-objects scan-tree-dump-times
optimized "\\* 10" 2
FAIL: gcc.dg/vect/pr53773.c scan-tree-dump-times optimized "\\* 10" 2
I confirmed that they are still present in trunk as of commit 829c0c06fe7b
"Fortran: improve diagnostic message for COMMON with automatic object
[PR32986]" from today.
The tests above fail with these messages found in gcc.log:
- gcc.dg/tree-ssa/slsr-11.c: pattern found 3 times
- gcc.dg/vect/bb-slp-29.c: pattern found 2 times
- gcc.dg/vect/pr53773.c: pattern found 0 times
Tested on Ubuntu 22.04 with:
$ ~/src/gcc/configure \
--disable-bootstrap \
--disable-multilib \
&& make -j 60 \
&& make -C gcc check-gcc RUNTESTFLAGS="gcc.dg/tree-ssa/tree-ssa.exp
gcc.dg/vect/vect.exp"
I'll attach gcc.log from trunk.
next reply other threads:[~2023-08-24 2:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 2:05 thiago.bauermann at linaro dot org [this message]
2023-08-24 7:41 ` [Bug middle-end/111125] [14 Regression] tree-ssa.exp and vect.exp failures after commit r14-3281-g99b5921bfc8f91 rguenth at gcc dot gnu.org
2023-08-24 8:15 ` rguenth at gcc dot gnu.org
2023-08-24 8:44 ` rguenth at gcc dot gnu.org
2023-08-24 8:54 ` rguenth at gcc dot gnu.org
2023-08-24 8:59 ` cvs-commit at gcc dot gnu.org
2023-08-24 9:36 ` cvs-commit at gcc dot gnu.org
2023-08-24 11:03 ` cvs-commit at gcc dot gnu.org
2023-08-24 11:03 ` rguenth at gcc dot gnu.org
2023-08-24 15:38 ` thiago.bauermann at linaro dot 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-111125-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).