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/103218] (a < 0) << signbit is not always optimized to a & signbitmask at the gimple level Date: Sat, 13 Nov 2021 01:59:36 +0000 [thread overview] Message-ID: <bug-103218-4-cVNLUgyMoG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103218-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103218 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-11-13 Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note another testcase: signed char f(signed char a) { if (a < 0) return 1u<<7; return 0; } PHIOPT does convert it to: _4 = a_2(D) < 0; _5 = (signed char) _4; _6 = _5 << 7; But then nothing converts it into: _6 = a_2(D) & 128; Let me see what I can do.
next prev parent reply other threads:[~2021-11-13 1:59 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-13 1:40 [Bug tree-optimization/103218] New: " pinskia at gcc dot gnu.org 2021-11-13 1:41 ` [Bug tree-optimization/103218] " pinskia at gcc dot gnu.org 2021-11-13 1:59 ` pinskia at gcc dot gnu.org [this message] 2021-11-13 2:11 ` pinskia at gcc dot gnu.org 2021-11-13 6:47 ` pinskia at gcc dot gnu.org 2021-11-13 20:15 ` pinskia at gcc dot gnu.org 2021-11-16 15:09 ` cvs-commit at gcc dot gnu.org 2021-11-16 15:10 ` 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-103218-4-cVNLUgyMoG@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).