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/106545] peephole.md seems like it should not exist
Date: Fri, 19 May 2023 05:14:30 +0000	[thread overview]
Message-ID: <bug-106545-4-qMx1dAuqu5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106545-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note I see XTheadMemPair code has been added to peephole.md which is good to
have it away. 
But again the first peephole is also handled differently already via
zero_extendsidi2_shifted which was added in r11-745-gd5cdcd5cf2b292 but it was
not until r13-4907-g2e886eef7f2b5a when we started to optimizing the following
code:
unsigned long f(unsigned long a)
{
  a <<= 32;
  a >>= 32;
  a <<= 10;
  return a;
}

      parent reply	other threads:[~2023-05-19  5:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06  4:59 [Bug target/106545] New: " pinskia at gcc dot gnu.org
2022-08-10 22:47 ` [Bug target/106545] " vineetg at rivosinc dot com
2023-05-19  5:02 ` pinskia at gcc dot gnu.org
2023-05-19  5:14 ` 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-106545-4-qMx1dAuqu5@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).