public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/99797] accessing uninitialized automatic variables Date: Tue, 20 Apr 2021 15:20:06 +0000 [thread overview] Message-ID: <bug-99797-4-4Hssmj4uv3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99797-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99797 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE CC| |msebor at gcc dot gnu.org Status|UNCONFIRMED |RESOLVED --- Comment #12 from Martin Sebor <msebor at gcc dot gnu.org> --- Sounds like this is effectively the same request as pr70069 for which there's a POC prototype: https://gcc.gnu.org/pipermail/gcc-patches/2021-February/565514.html Let's track the request there and resolve this as a duplicate. *** This bug has been marked as a duplicate of bug 70069 ***
prev parent reply other threads:[~2021-04-20 15:20 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-27 13:47 [Bug c/99797] New: " muecker at gwdg dot de 2021-03-27 19:19 ` [Bug c/99797] " pinskia at gcc dot gnu.org 2021-03-27 19:19 ` pinskia at gcc dot gnu.org 2021-03-28 6:32 ` muecker at gwdg dot de 2021-03-28 7:08 ` pinskia at gcc dot gnu.org 2021-03-28 7:16 ` pinskia at gcc dot gnu.org 2021-03-30 6:35 ` muecker at gwdg dot de 2021-04-14 20:18 ` muecker at gwdg dot de 2021-04-18 18:09 ` [Bug middle-end/99797] " pinskia at gcc dot gnu.org 2021-04-19 5:43 ` muecker at gwdg dot de 2021-04-19 10:43 ` vanyacpp at gmail dot com 2021-04-19 18:57 ` muecker at gwdg dot de 2021-04-20 15:20 ` msebor at gcc dot gnu.org [this message]
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-99797-4-4Hssmj4uv3@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).