public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/106105] New: new test case gcc.dg/torture/pr106070.c in r13-1243-gb36a1c964f9975 fails for 32 bits
@ 2022-06-27 13:24 seurer at gcc dot gnu.org
2022-06-27 18:23 ` [Bug testsuite/106105] " jakub at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: seurer at gcc dot gnu.org @ 2022-06-27 13:24 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106105
Bug ID: 106105
Summary: new test case gcc.dg/torture/pr106070.c in
r13-1243-gb36a1c964f9975 fails for 32 bits
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:b36a1c964f99758de1f3b169628965d3c3af812b, r13-1243-gb36a1c964f9975
This fails on both power 7 and 8 BE for 32 bits.
make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}'
dg-torture.exp=gcc.dg/torture/pr106070.c"
FAIL: gcc.dg/torture/pr106070.c -O0 execution test
FAIL: gcc.dg/torture/pr106070.c -O1 execution test
FAIL: gcc.dg/torture/pr106070.c -O2 execution test
FAIL: gcc.dg/torture/pr106070.c -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: gcc.dg/torture/pr106070.c -O3 -g execution test
FAIL: gcc.dg/torture/pr106070.c -Os execution test
FAIL: gcc.dg/torture/pr106070.c -O2 -flto -fno-use-linker-plugin
-flto-partition=none execution test
FAIL: gcc.dg/torture/pr106070.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects execution test
# of expected passes 8
# of unexpected failures 8
commit b36a1c964f99758de1f3b169628965d3c3af812b
Author: Richard Biener <rguenther@suse.de>
Date: Fri Jun 24 13:37:22 2022 +0200
middle-end/106070 - bogus cond-expr folding
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug testsuite/106105] new test case gcc.dg/torture/pr106070.c in r13-1243-gb36a1c964f9975 fails for 32 bits
2022-06-27 13:24 [Bug testsuite/106105] New: new test case gcc.dg/torture/pr106070.c in r13-1243-gb36a1c964f9975 fails for 32 bits seurer at gcc dot gnu.org
@ 2022-06-27 18:23 ` jakub at gcc dot gnu.org
2022-06-27 21:53 ` seurer at gcc dot gnu.org
2022-06-27 22:09 ` seurer at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: jakub at gcc dot gnu.org @ 2022-06-27 18:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106105
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Hasn't r13-1299-g00063459f683a fixed this already?
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug testsuite/106105] new test case gcc.dg/torture/pr106070.c in r13-1243-gb36a1c964f9975 fails for 32 bits
2022-06-27 13:24 [Bug testsuite/106105] New: new test case gcc.dg/torture/pr106070.c in r13-1243-gb36a1c964f9975 fails for 32 bits seurer at gcc dot gnu.org
2022-06-27 18:23 ` [Bug testsuite/106105] " jakub at gcc dot gnu.org
@ 2022-06-27 21:53 ` seurer at gcc dot gnu.org
2022-06-27 22:09 ` seurer at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: seurer at gcc dot gnu.org @ 2022-06-27 21:53 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106105
--- Comment #2 from seurer at gcc dot gnu.org ---
The last round of tests I ran still showed this failing but I will check with
the latest commit.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug testsuite/106105] new test case gcc.dg/torture/pr106070.c in r13-1243-gb36a1c964f9975 fails for 32 bits
2022-06-27 13:24 [Bug testsuite/106105] New: new test case gcc.dg/torture/pr106070.c in r13-1243-gb36a1c964f9975 fails for 32 bits seurer at gcc dot gnu.org
2022-06-27 18:23 ` [Bug testsuite/106105] " jakub at gcc dot gnu.org
2022-06-27 21:53 ` seurer at gcc dot gnu.org
@ 2022-06-27 22:09 ` seurer at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: seurer at gcc dot gnu.org @ 2022-06-27 22:09 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106105
seurer at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from seurer at gcc dot gnu.org ---
OK, it is fixed.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-06-27 22:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-27 13:24 [Bug testsuite/106105] New: new test case gcc.dg/torture/pr106070.c in r13-1243-gb36a1c964f9975 fails for 32 bits seurer at gcc dot gnu.org
2022-06-27 18:23 ` [Bug testsuite/106105] " jakub at gcc dot gnu.org
2022-06-27 21:53 ` seurer at gcc dot gnu.org
2022-06-27 22:09 ` seurer at gcc dot gnu.org
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).