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/106519] [13 Regression] internal compiler error: in gimple_phi_arg, at gimple.h:4594 by r13-1950 Date: Wed, 03 Aug 2022 21:54:46 +0000 [thread overview] Message-ID: <bug-106519-4-1VsZOfo1DV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106519-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106519 seurer at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seurer at gcc dot gnu.org --- Comment #1 from seurer at gcc dot gnu.org --- Seeing this on powerpc64 as well for FAIL: gcc.dg/torture/pr61346.c -O1 (internal compiler error: in gimple_phi_arg, at gimple.h:4594) FAIL: gcc.dg/torture/pr61346.c -O1 (test for excess errors) FAIL: gfortran.dg/make_unit.f90 -O1 (internal compiler error: in gimple_phi_arg, at gimple.h:4594) FAIL: gfortran.dg/make_unit.f90 -O1 (test for excess errors)
next prev parent reply other threads:[~2022-08-03 21:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-03 20:40 [Bug middle-end/106519] New: " hjl.tools at gmail dot com 2022-08-03 21:54 ` seurer at gcc dot gnu.org [this message] 2022-08-03 23:14 ` [Bug middle-end/106519] " tnfchris at gcc dot gnu.org 2022-08-04 7:42 ` marxin at gcc dot gnu.org 2022-08-04 7:42 ` marxin at gcc dot gnu.org 2022-08-04 9:32 ` rguenth at gcc dot gnu.org 2022-08-04 14:41 ` schwab@linux-m68k.org 2022-08-04 15:36 ` cvs-commit at gcc dot gnu.org 2022-08-04 15:42 ` marxin at gcc dot gnu.org 2022-08-04 15:49 ` tnfchris 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-106519-4-1VsZOfo1DV@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).