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/109959] `(a > 1) ? 0 : (a == 1)` is not optimized when spelled out at -O2+
Date: Sun, 06 Aug 2023 18:19:20 +0000	[thread overview]
Message-ID: <bug-109959-4-3bcbC7vOpn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109959-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109959

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=104296

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
For the bothone:
`(a > 1) ? 0 : a` could just be simplified to:
`(cast)(a == 1)` For unsigned types.

So:
(simplify
 (cond (gt @0 integer_onep@1) integer_zerop (convert? @0))
 (if (TYPE_UNSIGNED (TREE_TYPE (@0)))
  (convert (eq @0 @1))
 )
)

Turns out the optional convert in the above will catch both cases.

  parent reply	other threads:[~2023-08-06 18:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 22:10 [Bug tree-optimization/109959] New: `(a > 1) ? 0 : (a == 1)` is not optimized when spelled out pinskia at gcc dot gnu.org
2023-05-24 22:16 ` [Bug tree-optimization/109959] `(a > 1) ? 0 : (a == 1)` is not optimized when spelled out at -O2+ pinskia at gcc dot gnu.org
2023-05-24 22:17 ` pinskia at gcc dot gnu.org
2023-05-24 22:21 ` pinskia at gcc dot gnu.org
2023-05-25  3:39 ` pinskia at gcc dot gnu.org
2023-05-25  7:57 ` rguenth at gcc dot gnu.org
2023-06-07 22:36 ` pinskia at gcc dot gnu.org
2023-06-07 22:48 ` pinskia at gcc dot gnu.org
2023-08-06 18:19 ` pinskia at gcc dot gnu.org [this message]
2023-08-06 21:12 ` pinskia at gcc dot gnu.org
2023-08-07  0:26 ` pinskia at gcc dot gnu.org
2023-08-07  1:52 ` pinskia at gcc dot gnu.org
2023-08-07  5:09 ` pinskia at gcc dot gnu.org
2023-08-07 14:47 ` cvs-commit at gcc dot gnu.org
2023-08-07 14:48 ` 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-109959-4-3bcbC7vOpn@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: link
Be 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).