public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/102501] New: [12 regression] several test case failures after r12-3876
Date: Mon, 27 Sep 2021 17:42:02 +0000 [thread overview]
Message-ID: <bug-102501-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102501
Bug ID: 102501
Summary: [12 regression] several test case failures after
r12-3876
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:4a960d548b7d7d942f316c5295f6d849b74214f5, r12-3876
make -k check-gcc RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr66752-3.c"
FAIL: gcc.dg/tree-ssa/pr66752-3.c scan-tree-dump-not thread3 "if .flag"
# of expected passes 2
# of unexpected failures 1
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/tree-ssa/pr66752-3.c
-fdiagnostics-plain-output -O2 -fdump-tree-thread1-details -fdump-tree-thread3
-S -o pr66752-3.s
Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled2625074.cc
-fdiagnostics-plain-output -S -o exceptions_enabled2625074.s (timeout =
300)
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled2625074.cc
-fdiagnostics-plain-output -S -o exceptions_enabled2625074.s
PASS: gcc.dg/tree-ssa/pr66752-3.c (test for excess errors)
PASS: gcc.dg/tree-ssa/pr66752-3.c scan-tree-dump-times thread1 "Registering
jump" 2
FAIL: gcc.dg/tree-ssa/pr66752-3.c scan-tree-dump-not thread3 "if .flag"
testcase
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/tree-ssa/tree-ssa.exp
completed in 0 seconds
=== gcc Summary ===
# of expected passes 2
# of unexpected failures 1
There's a second one that fails here, too.
make -k check-gcc RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr77445-2.c"
FAIL: gcc.dg/tree-ssa/pr77445-2.c scan-tree-dump thread1 "Jumps threaded: 9"
# of expected passes 6
# of unexpected failures 1
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/tree-ssa/pr77445-2.c
-fdiagnostics-plain-output -O2 -fdisable-tree-evrp
-fdump-tree-thread-details-blocks-stats -S -o pr77445-2.s
cc1: note: disable pass tree-evrp for functions in the range of [0, 4294967295]
PASS: gcc.dg/tree-ssa/pr77445-2.c (test for excess errors)
FAIL: gcc.dg/tree-ssa/pr77445-2.c scan-tree-dump thread1 "Jumps threaded: 9"
PASS: gcc.dg/tree-ssa/pr77445-2.c scan-tree-dump-times thread1 "Invalid sum" 1
PASS: gcc.dg/tree-ssa/pr77445-2.c scan-tree-dump-not thread1 "optimizing for
size"
PASS: gcc.dg/tree-ssa/pr77445-2.c scan-tree-dump-not thread2 "optimizing for
size"
PASS: gcc.dg/tree-ssa/pr77445-2.c scan-tree-dump-not thread3 "optimizing for
size"
PASS: gcc.dg/tree-ssa/pr77445-2.c scan-tree-dump-not thread4 "optimizing for
size"
testcase
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/tree-ssa/tree-ssa.exp
completed in 0 seconds
=== gcc Summary ===
# of expected passes 6
# of unexpected failures 1
commit 4a960d548b7d7d942f316c5295f6d849b74214f5 (HEAD, refs/bisect/bad)
Author: Aldy Hernandez <aldyh@redhat.com>
Date: Thu Sep 23 10:59:24 2021 +0200
Avoid invalid loop transformations in jump threading registry.
next reply other threads:[~2021-09-27 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 17:42 seurer at gcc dot gnu.org [this message]
2021-09-28 8:34 ` [Bug testsuite/102501] " rguenth at gcc dot gnu.org
2021-09-28 15:31 ` aldyh at gcc dot gnu.org
2021-09-28 16:32 ` aldyh at gcc dot gnu.org
2021-09-29 18:28 ` cvs-commit at gcc dot gnu.org
2021-09-29 18:29 ` 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-102501-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).