public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/102857] [12 regression] r12-4526 caused regressions on ssa-dom-thread-7.c
Date: Fri, 22 Oct 2021 21:34:56 +0000 [thread overview]
Message-ID: <bug-102857-4-DIF2B1EOTY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102857-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102857
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |testsuite
CC| |aldyh at gcc dot gnu.org,
| |pinskia at gcc dot gnu.org
Status|UNCONFIRMED |NEW
Keywords|wrong-code |
Last reconfirmed| |2021-10-22
Ever confirmed|0 |1
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
/* { dg-final { scan-tree-dump "Jumps threaded: 12" "thread3" } } */
/* { dg-final { scan-tree-dump-not "Jumps threaded" "dom2" } } */
/* aarch64 has the highest CASE_VALUES_THRESHOLD in GCC. It's high enough
to change decisions in switch expansion which in turn can expose new
jump threading opportunities. Skip the later tests on aarch64. */
/* { dg-final { scan-tree-dump-not "Jumps threaded" "dom3" { target { !
aarch64*-*-* } } } } */
/* { dg-final { scan-tree-dump-not "Jumps threaded" "vrp-thread2" { target { !
aarch64*-*-* } } } } */
Someone didn't update this for aarch64 which is why you get:
gcc.dg/tree-ssa/ssa-dom-thread-7.c: dump file does not exist
UNRESOLVED: gcc.dg/tree-ssa/ssa-dom-thread-7.c scan-tree-dump-not vrp-thread2
"Jumps threaded"
On x86_64 also.
Christophe,
Can you file gcc.target/arm/ivopts-4.c seperately? Since it seems unrelated
to others. And this one can be for the ssa-dom-thread-7.c failure only.
next prev parent reply other threads:[~2021-10-22 21:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 12:40 [Bug middle-end/102857] New: [12 regression] r12-4526 caused regressions on vect/bb-slp-16.c and ssa-dom-thread-7.c clyon at gcc dot gnu.org
2021-10-20 13:46 ` [Bug middle-end/102857] " rguenth at gcc dot gnu.org
2021-10-21 1:42 ` pinskia at gcc dot gnu.org
2021-10-21 9:14 ` pinskia at gcc dot gnu.org
2021-10-22 21:29 ` [Bug middle-end/102857] [12 regression] r12-4526 caused regressions on ssa-dom-thread-7.c pinskia at gcc dot gnu.org
2021-10-22 21:34 ` pinskia at gcc dot gnu.org [this message]
2021-10-22 23:10 ` [Bug testsuite/102857] " clyon at gcc dot gnu.org
2021-10-23 7:04 ` aldyh at gcc dot gnu.org
2021-10-23 7:54 ` pinskia at gcc dot gnu.org
2021-10-23 7:56 ` pinskia at gcc dot gnu.org
2021-10-23 8:53 ` aldyh at gcc dot gnu.org
2021-10-23 8:53 ` aldyh at gcc dot gnu.org
2021-10-23 9:05 ` pinskia at gcc dot gnu.org
2021-10-23 9:07 ` aldyh at redhat dot com
2021-10-26 6:21 ` cvs-commit at gcc dot gnu.org
2021-10-26 6:43 ` aldyh 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-102857-4-DIF2B1EOTY@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).