public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jules 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: Thu, 11 Jan 2024 13:53:13 +0000 [thread overview] Message-ID: <bug-113317-4-0k9yi0hlbJ@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 jules at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jules at gcc dot gnu.org --- Comment #2 from jules at gcc dot gnu.org --- I haven't been able to reproduce this with our local testing infrastructure on the powerpc64le machine available to me (i.e., the test works for me there). I'd be a bit surprised about a machine dependence at this early stage in parsing, but here we go! Let me know if there's any other information that might help track this down.
next prev parent reply other threads:[~2024-01-11 13:53 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 [this message] 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 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-0k9yi0hlbJ@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).