public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105629] New: [13 Regression] g++.dg/opt/pr94589-2.C for cris, m68k, s390x
Date: Tue, 17 May 2022 15:22:47 +0000 [thread overview]
Message-ID: <bug-105629-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105629
Bug ID: 105629
Summary: [13 Regression] g++.dg/opt/pr94589-2.C for cris, m68k,
s390x
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: hp at gcc dot gnu.org
Target Milestone: ---
Created attachment 52987
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52987&action=edit
pr94589-2.C.252t.optimized
The test g++.dg/opt/pr94589-2.C is last known passing for cris-elf with
r13-172-g1e2334302d6ad5. For r13-211-g0c7bce0ac184c0 it failed, and has failed
since then, including r13-555-g1815462a6e53:
testrun output:
FAIL: g++.dg/opt/pr94589-2.C -std=gnu++20 scan-tree-dump-times optimized
"[ij]_[0-9]+\\(D\\) (?:<|<=|==|!=|>|>=) [ij]_[0-9]+\\(D\\)" 12
FAIL: g++.dg/opt/pr94589-2.C -std=gnu++20 scan-tree-dump-times optimized
"i_[0-9]+\\(D\\) (?:<|<=|==|!=|>|>=) 5\\.0" 12
In g++.log:
PASS: g++.dg/opt/pr94589-2.C -std=gnu++20 (test for excess errors)
g++.dg/opt/pr94589-2.C -std=gnu++20 : pattern found 14 times
FAIL: g++.dg/opt/pr94589-2.C -std=gnu++20 scan-tree-dump-times optimized
"[ij]_[0-9]+\\(D\\) (?:<|<=|==|!=|>|>=) [ij]_[0-9]+\\(D\\)" 12
g++.dg/opt/pr94589-2.C -std=gnu++20 : pattern found 14 times
FAIL: g++.dg/opt/pr94589-2.C -std=gnu++20 scan-tree-dump-times optimized
"i_[0-9]+\\(D\\) (?:<|<=|==|!=|>|>=) 5\\.0" 12
See attachment for contents of pr94589-2.C.252t.optimized at
r13-555-g1815462a6e53.
The test appears to fail in the same way according to gcc-testresults@, for
m68k-unknown-linux-gnu
(posts https://gcc.gnu.org/pipermail/gcc-testresults/2022-May/761149.html and
https://gcc.gnu.org/pipermail/gcc-testresults/2022-May/761602.html) and
s390x-ibm-linux-gnu (posts
https://gcc.gnu.org/pipermail/gcc-testresults/2022-May/761118.html and
https://gcc.gnu.org/pipermail/gcc-testresults/2022-May/761552.html).
next reply other threads:[~2022-05-17 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 15:22 hp at gcc dot gnu.org [this message]
2022-05-18 12:37 ` [Bug middle-end/105629] " rguenth at gcc dot gnu.org
2022-05-19 22:40 ` hp at gcc dot gnu.org
2022-05-20 6:07 ` rguenther at suse dot de
2022-05-20 11:43 ` hp at gcc dot gnu.org
2022-05-20 11:46 ` rguenther at suse dot de
2022-05-20 21:55 ` hp at gcc dot gnu.org
2022-05-21 1:26 ` hp at gcc dot gnu.org
2022-05-23 9:15 ` rguenth at gcc dot gnu.org
2022-05-24 6:20 ` cvs-commit at gcc dot gnu.org
2022-05-24 6:21 ` rguenth at gcc dot gnu.org
2022-05-24 14:02 ` hp 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-105629-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).