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 tree-optimization/101793] Incorrect -Wmaybe-uninitialized on an unreachable use at -O1 Date: Wed, 26 Jan 2022 17:56:50 +0000 [thread overview] Message-ID: <bug-101793-4-u6kTr4lFmN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101793-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101793 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Assignee|msebor at gcc dot gnu.org |unassigned at gcc dot gnu.org --- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> --- I'm not working on this anymore.
next prev parent reply other threads:[~2022-01-26 17:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-05 20:19 [Bug c/101793] New: Incorrect production of ‘may be used uninitialized in this function [-Werror=maybe-uninitialized]' thutt at vmware dot com 2021-08-05 20:20 ` [Bug c/101793] " thutt at vmware dot com 2021-08-05 20:33 ` [Bug tree-optimization/101793] " pinskia at gcc dot gnu.org 2021-08-05 20:59 ` thutt at vmware dot com 2021-08-05 21:14 ` pinskia at gcc dot gnu.org 2021-08-07 0:13 ` msebor at gcc dot gnu.org 2021-08-07 0:17 ` [Bug tree-optimization/101793] Incorrect -Wmaybe-uninitialized on an unreachable use at -O1 msebor at gcc dot gnu.org 2022-01-26 17:56 ` msebor at gcc dot gnu.org [this message] 2022-11-20 5:15 ` law 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-101793-4-u6kTr4lFmN@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).