public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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 16:07:59 +0000 [thread overview]
Message-ID: <bug-107679-4-NhSIyfGPcx@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
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:8a5f3663f8de45b7030dfe7ce962783dc1a19885
commit r13-4101-g8a5f3663f8de45b7030dfe7ce962783dc1a19885
Author: Richard Biener <rguenther@suse.de>
Date: Wed Nov 16 13:57:14 2022 +0100
middle-end/107679 - fix SSA rewrite of clobber of parameter
When the frontend clobbers a parameter and that parameter gets
rewritten into SSA then we ICE because we didn't expect this. Avoid
using the parameter decl to create a SSA default def in this case.
PR middle-end/107679
* tree-into-ssa.cc (maybe_register_def): Use new temporary if
we require an uninitialized value for a parameter decl.
* gfortran.dg/pr107679.f90: New testcase.
next prev parent reply other threads:[~2022-11-16 16:07 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 ` [Bug middle-end/107679] " rguenth at gcc dot gnu.org
2022-11-16 16:07 ` cvs-commit at gcc dot gnu.org [this message]
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-NhSIyfGPcx@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: link
Be 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).