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/110919] [14 Regression] Dead Code Elimination Regression at -O3 since r14-1691-gbc5a2c2e793
Date: Sun, 20 Aug 2023 18:36:23 +0000	[thread overview]
Message-ID: <bug-110919-4-gegUuhjssa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110919-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |pinskia at gcc dot gnu.org

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
After reassoc1 we have:


  _19 = _6 == iftmp.1_8;
  _3 = iftmp.1_8 ^ 1;
  _21 = (_Bool) _3;
  _23 = _6 != 0;
  _10 = _19 & _23;
  _5 = _10 & _21;


Which is: (_6 != 0) & (_6 == iftmp.1_8) But since we know that iftmp.1_8 only
has 2 values, we could optimize this to: (_6 == 1) & (iftmp.1_8 == 1)


Reduced testcase:
```
_Bool f(int a, int b)
{
  b &= 1;
  _Bool t = a == b;
  int c = b^1;
  _Bool d = c;
  _Bool e = a;
  _Bool g = t & d;
  _Bool h = g & e;
  return h;
}
```
This should return false always.

So something like:
(simplify
 (bit_and:c (eq:c @0 @1) (ne:c @0 INTEGER_CST@2))
 (if (has_two_value_range (@1))
  (with {
     tree other_value = ...;
   }
   (bit_and (eq @0 { other_value; }) (eq @1 { other_value; }))
  )
 )
)

  parent reply	other threads:[~2023-08-20 18:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 11:05 [Bug tree-optimization/110919] New: " scherrer.sv at gmail dot com
2023-08-06 11:35 ` [Bug tree-optimization/110919] " scherrer.sv at gmail dot com
2023-08-06 16:55 ` pinskia at gcc dot gnu.org
2023-08-06 17:12 ` pinskia at gcc dot gnu.org
2023-08-20  9:11 ` pinskia at gcc dot gnu.org
2023-08-20 18:36 ` pinskia at gcc dot gnu.org [this message]
2023-08-20 18:41 ` pinskia at gcc dot gnu.org
2023-09-04  5:53 ` pinskia at gcc dot gnu.org
2023-09-04  6:09 ` pinskia at gcc dot gnu.org
2023-09-04  6:55 ` pinskia at gcc dot gnu.org
2024-03-07 23:26 ` law at gcc dot gnu.org
2024-05-07  7:41 ` [Bug tree-optimization/110919] [14/15 " rguenth 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-110919-4-gegUuhjssa@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).