public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109139] [13 Regression] ice in make_decl_rtl, at varasm.cc:1442 Date: Wed, 15 Mar 2023 08:34:13 +0000 [thread overview] Message-ID: <bug-109139-4-yLHTqpuLYa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109139-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109139 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Target Milestone|--- |13.0 Summary|ice in make_decl_rtl, at |[13 Regression] ice in |varasm.cc:1442 |make_decl_rtl, at | |varasm.cc:1442 Keywords|needs-bisection |ice-on-valid-code Last reconfirmed| |2023-03-15 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Before we had: unsigned char link.9[0:18446744073709551615]; in the referenced variables but after it is gone. But it is still referened: MEM[(int[0:D.2753] *)&link.9] = .DEFERRED_INIT (0, 2, &"link"[0]); release_ssa removes it but I have not looked into how. Note the way ccp1 turns this VLA into a non-VLA might be an issue too ...
next prev parent reply other threads:[~2023-03-15 8:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-15 8:17 [Bug c/109139] New: " dcb314 at hotmail dot com 2023-03-15 8:34 ` pinskia at gcc dot gnu.org [this message] 2023-03-15 8:36 ` [Bug tree-optimization/109139] [13 Regression] " pinskia at gcc dot gnu.org 2023-03-15 8:43 ` rguenth at gcc dot gnu.org 2023-03-15 9:29 ` cvs-commit at gcc dot gnu.org 2023-03-15 9:30 ` 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-109139-4-yLHTqpuLYa@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).