public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105990] New: Dead code elimination failed at -O3 Date: Wed, 15 Jun 2022 13:35:16 +0000 [thread overview] Message-ID: <bug-105990-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105990 Bug ID: 105990 Summary: Dead code elimination failed at -O3 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: crazylht at gmail dot com Target Milestone: --- static struct { int a; } b, c; static int d = -1; void foo(); int main() { if (b.a) d = 2 | (b.a <= 0); for (; b.a; b.a++) c = b; if (!d) foo(); } foo() can be eliminated since d would never be zero.
next reply other threads:[~2022-06-15 13:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-15 13:35 crazylht at gmail dot com [this message] 2022-06-15 13:39 ` [Bug tree-optimization/105990] " crazylht at gmail dot com 2022-06-16 13:32 ` Painololo at protonmail dot com 2022-06-21 1:38 ` pinskia at gcc dot gnu.org 2023-08-07 20:56 ` [Bug ipa/105990] " pinskia at gcc dot gnu.org 2023-10-25 22:19 ` pinskia 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-105990-4@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).