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/103216] missed optimization, phiopt/vrp?
Date: Sat, 13 Nov 2021 04:52:27 +0000	[thread overview]
Message-ID: <bug-103216-4-nIgHE6fxKM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103216-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3) 
> I am going to implement this.  I think I only need the first conversion (and
> making sure cond goes away which leads to the second one) which should lead
> to the rest (after having fixed PR 103218 which I am doing first which is
> needed to get the 4th line).

I was right and wrong. I still need to debug match-and-simplify for why ! does
not work in one case, I thought it would.

Also the last 5 steps did not happen either on the gimple level, I filed PR
103220 for that.

  parent reply	other threads:[~2021-11-13  4:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13  0:25 [Bug tree-optimization/103216] New: " pinskia at gcc dot gnu.org
2021-11-13  0:39 ` [Bug tree-optimization/103216] " pinskia at gcc dot gnu.org
2021-11-13  1:51 ` pinskia at gcc dot gnu.org
2021-11-13  3:58 ` pinskia at gcc dot gnu.org
2021-11-13  3:58 ` pinskia at gcc dot gnu.org
2021-11-13  4:52 ` pinskia at gcc dot gnu.org [this message]
2021-11-13 22:16 ` pinskia at gcc dot gnu.org
2021-11-13 23:01 ` pinskia at gcc dot gnu.org
2021-11-15  0:10 ` pinskia at gcc dot gnu.org
2021-11-16 15:10 ` pinskia at gcc dot gnu.org
2021-12-20 14:45 ` mcccs at gmx dot com
2023-06-07 15:17 ` pinskia at gcc dot gnu.org
2023-10-14  4:45 ` 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-103216-4-nIgHE6fxKM@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).