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/101805] New: Max<bool0,bool1> -> bool0 | bool1 Min<bool0, bool1> -> a & b
Date: Fri, 06 Aug 2021 20:11:07 +0000	[thread overview]
Message-ID: <bug-101805-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101805
           Summary: Max<bool0,bool1> -> bool0 | bool1 Min<bool0, bool1> ->
                    a & b
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

Take:
int maxbool(bool ab, bool bb)
{
  int a = ab;
  int b = bb;
  int c;
  c = (a > b)?a : b;
  return c;
}
int minbool(bool ab, bool bb)
{
  int a = ab;
  int b = bb;
  int c;
  c = (a < b)?a : b;
  return c;
}
---- CUT ----
These two should be optimized to just:
int maxbool_or(bool ab, bool bb)
{
  int c = ab | bb;
  return c;
}
int minbool_and(bool ab, bool bb)
{
  int c = ab & bb;
  return c;
}
------ CUT----

GCC, ICC, clang nor MSVC do this optimization.

             reply	other threads:[~2021-08-06 20:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 20:11 pinskia at gcc dot gnu.org [this message]
2021-08-06 21:50 ` [Bug tree-optimization/101805] " pinskia at gcc dot gnu.org
2021-08-14  0:21 ` pinskia at gcc dot gnu.org
2022-02-21  3:26 ` pinskia at gcc dot gnu.org
2022-11-27  7:04 ` pinskia at gcc dot gnu.org
2023-05-15 21:51 ` pinskia at gcc dot gnu.org
2023-05-16  1:38 ` pinskia at gcc dot gnu.org
2023-05-16  3:53 ` 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-101805-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: 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).