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 middle-end/110316] [11/12/13/14 Regression] g++.dg/ext/timevar1.C and timevar2.C fail erratically Date: Wed, 20 Mar 2024 19:50:34 +0000 [thread overview] Message-ID: <bug-110316-4-1vAn4roEm0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110316-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110316 --- Comment #6 from seurer at gcc dot gnu.org --- Was this only fixed for trunk? I started seeing it for gcc 13: g:5b928badac560ad48e0e9fc480096ff396d9d9c6, r13-8468-g5b928badac560a make -k check-gcc RUNTESTFLAGS="dg.exp=g++.dg/ext/timevar1.C" FAIL: g++.dg/ext/timevar1.C -std=gnu++98 (internal compiler error: in validate_phases, at timevar.cc:626) FAIL: g++.dg/ext/timevar1.C -std=gnu++98 (test for excess errors) # of expected passes 7 # of unexpected failures 2
next prev parent reply other threads:[~2024-03-20 19:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-20 0:21 [Bug testsuite/110316] New: [14 regression] " seurer at gcc dot gnu.org 2023-06-20 6:58 ` [Bug middle-end/110316] [10/11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-07-07 10:45 ` [Bug middle-end/110316] [11/12/13/14 " rguenth at gcc dot gnu.org 2023-07-21 17:47 ` pinskia at gcc dot gnu.org 2023-08-04 10:29 ` cvs-commit at gcc dot gnu.org 2024-02-21 7:12 ` pinskia at gcc dot gnu.org 2024-03-20 19:50 ` seurer at gcc dot gnu.org [this message] 2024-03-20 20:32 ` pinskia 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-110316-4-1vAn4roEm0@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).