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 target/115086] bic is not used when the non-not part is a constant
Date: Wed, 15 May 2024 05:11:34 +0000	[thread overview]
Message-ID: <bug-115086-4-CFnxVEAwvQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115086-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #2)
> And perhaps more importantly the mov can even be hoisted outside of a loop.

That won't be happening right away, see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112304#c4 where cinc has the same
issue. In this case it is very similar in that we don't pull the constant from
the and (rather than add) inside LIM. Basically we don't have an early
"combine" to even generate the and/not pattern, forwprop could but I Have not
looked into why it does not and then we could do a split afterwards and LIM
might be able to pull it out. I will definitely look into that but that will
step 2 of this and the other issue.

  parent reply	other threads:[~2024-05-15  5:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14  9:45 [Bug target/115086] New: " pinskia at gcc dot gnu.org
2024-05-14  9:49 ` [Bug target/115086] " pinskia at gcc dot gnu.org
2024-05-14  9:50 ` rearnsha at gcc dot gnu.org
2024-05-15  5:11 ` pinskia at gcc dot gnu.org [this message]
2024-05-15  7:38 ` pinskia at gcc dot gnu.org
2024-05-15 10:37 ` 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-115086-4-CFnxVEAwvQ@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).