From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 27C0D3858D1E; Tue, 20 Jun 2023 00:21:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 27C0D3858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1687220504; bh=RiwycQGJUokPNO1d5JT2FbeQ2yQhh+HTrDHgycnrbKM=; h=From:To:Subject:Date:From; b=fCJXQiNwTHhlj6VE3+LK/hGqHe3GVGMTAWmH31D+3VNxceDyfgUhpay2xxlkG5N7G hkgfXtq9RBAhxJjc8Az+Ll10liuuk48TKnXhd3nKaY+0MfUc9r7Ccm65M/rX+VLIQO zMond6MHmfrF1OQxZ/F+GRQmvjDuGLlbpXk7HW4c= From: "seurer at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/110316] New: [14 regression] g++.dg/ext/timevar1.C and timevar2.C fail erratically Date: Tue, 20 Jun 2023 00:21:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: seurer at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110316 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 workin= g on the next. It is happening on one of our newer/faster machines but it did n= ot 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=3Dgnu++17 (internal compiler error: in validate_phases, at timevar.cc:626) FAIL: g++.dg/ext/timevar1.C -std=3Dgnu++17 (test for excess errors) FAIL: g++.dg/ext/timevar2.C -std=3Dgnu++20 (internal compiler error: in validate_phases, at timevar.cc:626) FAIL: g++.dg/ext/timevar2.C -std=3Dgnu++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-gn= u/libstdc++-v3/include/powerpc64le-unknown-linux-gnu -I/home/gccbuild/build/nightly/build-gcc-trunk/powerpc64le-unknown-linux-gn= u/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=3D0 -std=3Dgnu++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 (1= 00%) 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 (1= 00%) 174k ( 5%)^M parser (global) : 0.01 (100%) 0.00 ( 0%) 0.00 ( = 0%) 587k ( 17%)^M TOTAL : 0.01 0.00 0.01=20= =20=20=20=20=20=20 3496k^M Extra diagnostic checks enabled; compiler may run slowly.^M Configure with --enable-checking=3Drelease 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?=