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/101024] Missed min expression at phiopt1
Date: Thu, 01 Jun 2023 02:07:33 +0000	[thread overview]
Message-ID: <bug-101024-4-Oe3BblO3zA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101024-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
A few testcases that have not been added to the testsuite yet.
Note it takes f1 to phiopt2 to optimize that because there is an extra
statement left behind because match does not deal with `(signed)a < 0` yet.

```
unsigned long long
f2 (unsigned long long x)
{
  if (x < 0x8000000000000000ULL)
    x = 0x8000000000000000ULL;
  else
    {
        if (x >= 0x8000000000000023ULL)
          x = 0x8000000000000023ULL;
    }
  return x;
}
unsigned long long
f1 (unsigned long long x)
{
  if (x >= 100)
    {
        if (x >= 0x8000000000000000ULL)
          x = 0x8000000000000000ULL;
    }
  else
    x = 100;
  return x;
}

```

      parent reply	other threads:[~2023-06-01  2:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  4:00 [Bug tree-optimization/101024] New: " pinskia at gcc dot gnu.org
2021-06-11  4:01 ` [Bug tree-optimization/101024] " pinskia at gcc dot gnu.org
2021-06-11 11:44 ` pinskia at gcc dot gnu.org
2021-07-06  7:28 ` pinskia at gcc dot gnu.org
2021-07-09  7:22 ` pinskia at gcc dot gnu.org
2021-07-20 21:20 ` pinskia at gcc dot gnu.org
2023-04-05 19:33 ` pinskia at gcc dot gnu.org
2023-05-07 23:44 ` pinskia at gcc dot gnu.org
2023-05-08  1:52 ` pinskia at gcc dot gnu.org
2023-05-08  2:17 ` pinskia at gcc dot gnu.org
2023-05-30 16:26 ` pinskia at gcc dot gnu.org
2023-06-01  2:07 ` pinskia at gcc dot gnu.org [this message]

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-101024-4-Oe3BblO3zA@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).