public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/113317] New test case libgomp.c++/ind-base-2.C fails with ICE Date: Fri, 19 Jan 2024 16:41:51 +0000 [thread overview] Message-ID: <bug-113317-4-MuLFIcPF4R@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113317-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113317 --- Comment #8 from Peter Bergner <bergner at gcc dot gnu.org> --- ...unless the other P9 systems that were tested built with those "broken" versions of the compilers. If that's the case, then it points to something else wrong on that system.
next prev parent reply other threads:[~2024-01-19 16:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-10 21:30 [Bug other/113317] New: " seurer at gcc dot gnu.org 2024-01-10 21:59 ` [Bug other/113317] " bergner at gcc dot gnu.org 2024-01-11 13:53 ` jules at gcc dot gnu.org 2024-01-17 8:06 ` linkw at gcc dot gnu.org 2024-01-18 18:39 ` seurer at gcc dot gnu.org 2024-01-18 19:12 ` jules at gcc dot gnu.org 2024-01-18 21:50 ` seurer at gcc dot gnu.org 2024-01-19 15:24 ` bergner at gcc dot gnu.org 2024-01-19 16:41 ` bergner at gcc dot gnu.org [this message] 2024-04-18 19:23 ` tschwinge 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-113317-4-MuLFIcPF4R@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).