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/73550] Another wrong -Wmaybe-uninitialized warning in switch statement Date: Tue, 30 Aug 2022 13:13:30 +0000 [thread overview] Message-ID: <bug-73550-4-TMdXVLF94A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-73550-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=73550 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- Note the main issue is that we don't handle the case where an edge from a switch reaches a case with more than a single case value. There's a representational issue here in the predicate analysis code - one would think that amending it with a new "kind" implementing a falls-in-range operation and recording an irange (but conservative precise or lose depending on who is asking, so maybe better "exact") would be a good fix, possibly also handling range checking in general this way.
next prev parent reply other threads:[~2022-08-30 13:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-73550-4@http.gcc.gnu.org/bugzilla/> 2021-03-31 22:46 ` [Bug middle-end/73550] " msebor at gcc dot gnu.org 2022-08-30 11:43 ` [Bug tree-optimization/73550] " rguenth at gcc dot gnu.org 2022-08-30 12:39 ` rguenth at gcc dot gnu.org 2022-08-30 13:13 ` rguenth at gcc dot gnu.org [this message] 2022-08-30 13:38 ` cvs-commit at gcc dot gnu.org 2022-08-31 6:52 ` rguenth at gcc dot gnu.org 2022-08-31 11:04 ` cvs-commit at gcc dot gnu.org 2022-08-31 11:05 ` 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-73550-4-TMdXVLF94A@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).