public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102560] [12 Regression] g++.dg/Walloca1.C ICE with aggressive GC Date: Sat, 02 Oct 2021 19:53:05 +0000 [thread overview] Message-ID: <bug-102560-4-2GmpgniNxW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102560-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102560 --- Comment #3 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- Probably needs GTY markers, and possibly putting it invalid_range in file scope.
next prev parent reply other threads:[~2021-10-02 19:53 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-02 0:59 [Bug tree-optimization/102560] New: " jason at gcc dot gnu.org 2021-10-02 14:12 ` [Bug tree-optimization/102560] " pinskia at gcc dot gnu.org 2021-10-02 16:35 ` aldyh at gcc dot gnu.org 2021-10-02 16:48 ` aldyh at gcc dot gnu.org 2021-10-02 19:53 ` aldyh at gcc dot gnu.org [this message] 2021-10-03 17:51 ` aldyh at gcc dot gnu.org 2021-10-04 6:59 ` rguenth at gcc dot gnu.org 2021-10-04 6:59 ` rguenth at gcc dot gnu.org 2021-10-04 7:02 ` aldyh at gcc dot gnu.org 2021-10-04 11:20 ` cvs-commit at gcc dot gnu.org 2021-10-04 11:21 ` aldyh 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-102560-4-2GmpgniNxW@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).