public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102872] If statement is always false but not figured out at gimple level Date: Thu, 21 Oct 2021 08:28:18 +0000 [thread overview] Message-ID: <bug-102872-4-0fkqSZ6PXc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102872-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102872 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note this does not get optimized at the rtl level on all targets either, e.g. aarch64 we get: tst w0, 65535 and w0, w0, 65535 ccmp w0, 0, 4, eq beq .L3 bl foo
next prev parent reply other threads:[~2021-10-21 8:28 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-21 8:25 [Bug tree-optimization/102872] New: " pinskia at gcc dot gnu.org 2021-10-21 8:28 ` pinskia at gcc dot gnu.org [this message] 2021-10-21 8:58 ` [Bug tree-optimization/102872] " rguenth at gcc dot gnu.org 2021-11-20 8:59 ` pinskia at gcc dot gnu.org 2021-11-22 11:17 ` rguenth at gcc dot gnu.org 2022-10-13 15:29 ` cvs-commit at gcc dot gnu.org 2022-10-13 17:02 ` amacleod at redhat dot com 2022-11-28 22:41 ` 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-102872-4-0fkqSZ6PXc@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).