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: Wed, 31 Aug 2022 06:52:18 +0000 [thread overview] Message-ID: <bug-73550-4-UaM1Qfs2ml@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 --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> --- Another thing we have is that with After normalization [USE]: fp_5 (a.3_4, b.2_3); is conditional on: ((_27 & 20500) AND (NOT (_26 != 0)) AND (NOT (_20 > 14))) and After normalization [DEF]: fp_5 = PHI <fun1(6), fun3(24), fp_11(D)(21), fun2(3), fun3(26)> is conditional on: ((code_9(D) == 2)) OR ((code_9(D) <= 4) AND (code_9(D) >= 3)) OR ((code_9(D) == 1)) OR ((code_9(D) == 12)) OR ((code_9(D) <= 14) AND (code_9(D) >= 13)) OR ((code_9(D) == 11)) the negated _26 != 0 predicate is not "normalized", it's defined as _20 = (unsigned int) code_9(D); ... _27 = 1 << _20; _26 = _27 & 480; so ultimatively switch lowering lowers the second switch statement which confuses us greatly here. OTOH without switch lowering we'd fail to process the use predicate because it's reached by multiple case labels. Solving this case fully is going to be interesting, but I have some more incremental improvements here.
next prev parent reply other threads:[~2022-08-31 6:52 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 2022-08-30 13:38 ` cvs-commit at gcc dot gnu.org 2022-08-31 6:52 ` rguenth at gcc dot gnu.org [this message] 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-UaM1Qfs2ml@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).