public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101853] [12/13/14 Regression] g++.dg/modules/xtreme-header-5_b.C ICE Date: Thu, 18 May 2023 18:23:57 +0000 [thread overview] Message-ID: <bug-101853-4-H4FJBV3gJa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101853-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101853 --- Comment #18 from Hans-Peter Nilsson <hp at gcc dot gnu.org> --- (In reply to Jiu Fu Guo from comment #17) > > But "nobody" counts that close, so better say "no xtreme-header-* failures > > since r13-5702-g72058eea9d407e". > > :) Since these failures occur erratically, They did at the time for cris-elf (too), but I believe the cause of *those* failures has been fixed. > so maybe reopen this or open a > new one if the failures are reproduced. That's the idea. :) > As two xtreme-header-5_ failures (not ICE) occur in Results for 14.0.0 > 20230518: https://gcc.gnu.org/pipermail/gcc-testresults/2023-May/784674.html. Good to know, but not for cris-elf.
prev parent reply other threads:[~2023-05-18 18:23 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-10 20:00 [Bug c++/101853] New: [12 " hp at gcc dot gnu.org 2021-08-10 20:02 ` [Bug c++/101853] " redi at gcc dot gnu.org 2021-08-10 20:04 ` hp at gcc dot gnu.org 2021-08-11 7:25 ` rguenth at gcc dot gnu.org 2021-08-11 20:12 ` seurer at gcc dot gnu.org 2021-08-13 0:55 ` hp at gcc dot gnu.org 2021-10-11 15:29 ` seurer at gcc dot gnu.org 2021-11-14 18:26 ` hp at gcc dot gnu.org 2021-11-14 19:12 ` redi at gcc dot gnu.org 2021-11-26 22:01 ` hp at gcc dot gnu.org 2021-11-27 10:05 ` hp at gcc dot gnu.org 2022-01-17 13:56 ` rguenth at gcc dot gnu.org 2022-04-01 5:29 ` guojiufu at gcc dot gnu.org 2022-05-06 8:30 ` [Bug c++/101853] [12/13 " jakub at gcc dot gnu.org 2023-05-08 12:22 ` [Bug c++/101853] [12/13/14 " rguenth at gcc dot gnu.org 2023-05-17 8:01 ` guojiufu at gcc dot gnu.org 2023-05-17 23:50 ` hp at gcc dot gnu.org 2023-05-17 23:56 ` hp at gcc dot gnu.org 2023-05-18 4:49 ` guojiufu at gcc dot gnu.org 2023-05-18 18:23 ` hp at gcc dot gnu.org [this message]
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-101853-4-H4FJBV3gJa@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).