public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Tue, 26 Oct 2021 06:21:13 +0000 [thread overview] Message-ID: <bug-102857-4-y2e4F79pK0@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 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>: https://gcc.gnu.org/g:4e417eea8f3f14131f7370f9bd5dd568611d11df commit r12-4701-g4e417eea8f3f14131f7370f9bd5dd568611d11df Author: Aldy Hernandez <aldyh@redhat.com> Date: Sat Oct 23 08:59:24 2021 +0200 [PR testsuite/102857] Tweak ssa-dom-thread-7.c for aarch64. First, ssa-dom-thread-7 was looking at a dump file that was not being generated. This probably happened in the detangling of the VRP threader from VRP, and I didn't notice because the test came back as with UNRESOLVED instead of FAIL. Second, aarch64 gets far more threads than other architectures (20 versus 12). The difference is sufficiently different to make the regex awkward. We already have special casing for aarch64 in other parts of this test, so perhaps it's simplest to have an arch specific test for the thread3 count. I don't know perhaps there's a better way. I wake up with chills in the middle of the night thinking about this test ;-). Tested on x86-64 Linux and aarch64 Linux. gcc/testsuite/ChangeLog: PR testsuite/102857 * gcc.dg/tree-ssa/ssa-dom-thread-7.c: Add -fdump-tree-vrp2-stats. Tweak for aarch64.
next prev parent reply other threads:[~2021-10-26 6:21 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 ` [Bug testsuite/102857] " pinskia at gcc dot gnu.org 2021-10-22 23:10 ` 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 [this message] 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-y2e4F79pK0@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: linkBe 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).