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/108933] [10/11/12/13 Regression] Missing rev16 detection
Date: Wed, 15 Mar 2023 22:09:15 +0000 [thread overview]
Message-ID: <bug-108933-4-98xj66Z1a9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108933-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108933
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[10/11/12/13 Regression] |[10/11/12/13 Regression]
|Missing bswap detection |Missing rev16 detection
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #1)
> As mentioned in the other PR, this isn't a bswap. If the bswap pass should
> optimize this, there would need to be a new optab for this and corresponding
> internal function,
> which bswap patch could use if the optab is defined.
Sorry I forgot to change the summary here. Anyways yes rev16 is not bswap.
next prev parent reply other threads:[~2023-03-15 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 19:50 [Bug target/108933] New: [10/11/12/13 Regression] Missing bswap detection pinskia at gcc dot gnu.org
2023-02-25 19:51 ` [Bug target/108933] " pinskia at gcc dot gnu.org
2023-03-10 17:54 ` pinskia at gcc dot gnu.org
2023-03-15 11:44 ` jakub at gcc dot gnu.org
2023-03-15 22:09 ` pinskia at gcc dot gnu.org [this message]
2023-03-15 22:10 ` [Bug target/108933] [10/11/12/13 Regression] Missing rev16 detection pinskia at gcc dot gnu.org
2023-03-27 10:56 ` rguenth at gcc dot gnu.org
2023-07-07 10:44 ` [Bug target/108933] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-01-29 15:58 ` cvs-commit at gcc dot gnu.org
2024-01-29 16:01 ` [Bug target/108933] [11/12/13 " rearnsha 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-108933-4-98xj66Z1a9@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).