public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/107679] [13 Regression] ICE in maybe_register_def, at tree-into-ssa.cc:1914 Date: Wed, 16 Nov 2022 12:55:43 +0000 [thread overview] Message-ID: <bug-107679-4-PT0StLXgBw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107679-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107679 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|fortran |middle-end Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|NEW |ASSIGNED Priority|P4 |P3 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Kind-of, yes. Somehow 'z' got marked for renaming, probably because we removed a TREE_ADDRESABLE flag. The SSA rewrite wants to replace <bb 2> [local count: 1073741824]: z ={v} {CLOBBER}; return; with an "uninitialized" def, but for PARM_DECLs the default def would be the actual parameter value. There's nothing wrong with clobbering 'z' I think, just the into-ssa code isn't prepared for this - the fix would be to create an anonymous default def in this case.
next prev parent reply other threads:[~2022-11-16 12:55 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-14 17:25 [Bug fortran/107679] New: " gscfq@t-online.de 2022-11-14 18:07 ` [Bug fortran/107679] " anlauf at gcc dot gnu.org 2022-11-14 18:22 ` anlauf at gcc dot gnu.org 2022-11-16 12:55 ` rguenth at gcc dot gnu.org [this message] 2022-11-16 16:07 ` [Bug middle-end/107679] " cvs-commit at gcc dot gnu.org 2022-11-17 7:50 ` rguenth 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-107679-4-PT0StLXgBw@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).