public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109714] bogus "may be used uninitialized warning" Date: Thu, 04 May 2023 06:07:27 +0000 [thread overview] Message-ID: <bug-109714-4-PLh9VxSbRS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109714-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109714 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- This is likely a duplicate, the issue is that uninit diagnostics do not cope well with loops and use/def predicates that eventually involve PHIs with backedges.
next prev parent reply other threads:[~2023-05-04 6:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-03 14:13 [Bug c/109714] New: bogus may be used uninitialized warning david at ixit dot cz 2023-05-03 18:08 ` [Bug tree-optimization/109714] bogus "may be used uninitialized warning" pinskia at gcc dot gnu.org 2023-05-04 6:07 ` rguenth at gcc dot gnu.org [this message] 2023-05-04 18:40 ` david at ixit dot cz 2023-05-04 18:41 ` pinskia at gcc dot gnu.org 2023-05-04 18:47 ` [Bug tree-optimization/109714] mesa/aux/draw_llvm: " pinskia at gcc dot gnu.org 2023-05-05 8:51 ` david at ixit dot cz 2023-05-05 16:20 ` pinskia at gcc dot gnu.org 2023-05-05 16:25 ` pinskia at gcc dot gnu.org 2023-05-05 19:11 ` david at ixit dot cz 2023-05-05 20:19 ` david at ixit dot cz
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-109714-4-PLh9VxSbRS@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).