https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110316
Bug ID: 110316
Summary: [14 regression] g++.dg/ext/timevar1.C and timevar2.C
fail erratically
Product: gcc
Version: 14.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: ---
I unfortunately do not have a clear starting point for this but recently the
g++.dg/ext/timevar1.C and timevar2 tests began failing some runs and working on
the next. It is happening on one of our newer/faster machines but it did not
used to fail there.
The last run I did not see any failures (for this ome nor previously) was
47fa3cef59a031f1b0fdce309ff634fab717606d, r14-1906-g47fa3cef59a031
The first run with failures was 0f9bb3e7a4aab95fd449f60b5f891ed9a6e5f352,
r14-1910-g0f9bb3e7a4aab9
I don't see anything in that range that might cause this, though.
FAIL: g++.dg/ext/timevar1.C -std=gnu++17 (internal compiler error: in
validate_phases, at timevar.cc:626)
FAIL: g++.dg/ext/timevar1.C -std=gnu++17 (test for excess errors)
FAIL: g++.dg/ext/timevar2.C -std=gnu++20 (internal compiler error: in
validate_phases, at timevar.cc:626)
FAIL: g++.dg/ext/timevar2.C -std=gnu++20 (test for excess errors)
spawn -ignore SIGHUP
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/testsuite/g++1/../../xg++
-B/home/gccbuild/build/nightly/build-gcc-trunk/gcc/testsuite/g++1/../../
/home/gccbuild/gcc_trunk_git/gcc/gcc/testsuite/g++.dg/ext/timevar2.C
-fdiagnostics-plain-output -nostdinc++
-I/home/gccbuild/build/nightly/build-gcc-trunk/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/powerpc64le-unknown-linux-gnu
-I/home/gccbuild/build/nightly/build-gcc-trunk/powerpc64le-unknown-linux-gnu/libstdc++-v3/include
-I/home/gccbuild/gcc_trunk_git/gcc/libstdc++-v3/libsupc++
-I/home/gccbuild/gcc_trunk_git/gcc/libstdc++-v3/include/backward
-I/home/gccbuild/gcc_trunk_git/gcc/libstdc++-v3/testsuite/util
-fmessage-length=0 -std=gnu++98 -ftime-report -S -o timevar2.s^M
^M
Time variable usr sys wall
GGC^M
phase setup : 0.00 ( 0%) 0.00 ( 0%) 0.01 (100%)
2835k ( 81%)^M
phase parsing : 0.01 (100%) 0.00 ( 0%) 0.00 ( 0%)
603k ( 17%)^M
|name lookup : 0.00 ( 0%) 0.00 ( 0%) 0.01 (100%)
174k ( 5%)^M
parser (global) : 0.01 (100%) 0.00 ( 0%) 0.00 ( 0%)
587k ( 17%)^M
TOTAL : 0.01 0.00 0.01
3496k^M
Extra diagnostic checks enabled; compiler may run slowly.^M
Configure with --enable-checking=release to disable checks.^M
Timing error: total of phase timers exceeds total time.^M
wall 1.000002666800281492e-02 > 1.000000150810810562e-02^M
internal compiler error: in validate_phases, at timevar.cc:626^M
0x10ff92bb toplev::~toplev()^M
/home/gccbuild/gcc_trunk_git/gcc/gcc/toplev.cc:2155^M
xg++: internal compiler error: Segmentation fault signal terminated program
cc1plus^M
Note that the two phase timings are both 0.01 and both report 100% while the
total time is also 0.01. Is this maybe a rounding issue?
