public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100866] PPC: Inefficient code for vec_revb(vector unsigned short) < P9
Date: Wed, 02 Jun 2021 15:03:47 +0000 [thread overview]
Message-ID: <bug-100866-4-OHCBQ6rroC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100866-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100866
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|powerpc-*-*-* |powerpc*
Severity|normal |enhancement
Last reconfirmed| |2021-06-02
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Confirmed. There are other ways to write this in two insns, but this
is probably the cheapest and simplest, and the immediate can be reused
potentially.
next prev parent reply other threads:[~2021-06-02 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 7:14 [Bug target/100866] New: " jens.seifert at de dot ibm.com
2021-06-02 15:03 ` segher at gcc dot gnu.org [this message]
2021-06-15 9:22 ` [Bug target/100866] " luoxhu at gcc dot gnu.org
2021-06-15 9:56 ` luoxhu at gcc dot gnu.org
2021-06-15 13:50 ` segher at gcc dot gnu.org
2021-06-16 5:53 ` luoxhu at gcc dot gnu.org
2021-06-18 1:37 ` luoxhu at gcc dot gnu.org
2021-06-18 8:32 ` jens.seifert at de dot ibm.com
2021-06-21 2:29 ` luoxhu at gcc dot gnu.org
2021-06-21 4:20 ` jens.seifert at de dot ibm.com
2021-06-21 12:42 ` wschmidt at gcc dot gnu.org
2021-06-21 12:46 ` wschmidt at gcc dot gnu.org
2021-06-21 19:27 ` segher at gcc dot gnu.org
2021-06-22 2:05 ` luoxhu at gcc dot gnu.org
2021-06-23 20:06 ` segher at gcc dot gnu.org
2022-11-02 8:42 ` cvs-commit at gcc dot gnu.org
2022-12-01 2:07 ` cvs-commit at gcc dot gnu.org
2022-12-14 5:52 ` guihaoc 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-100866-4-OHCBQ6rroC@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).