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/106770] PPCLE: Unnecessary xxpermdi before mfvsrd
Date: Tue, 28 Feb 2023 16:57:45 +0000 [thread overview]
Message-ID: <bug-106770-4-dIHetAcyNR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106770-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106770
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Target|powerpc |powerpc64le
Last reconfirmed| |2023-02-28
Ever confirmed|0 |1
--- Comment #7 from Segher Boessenkool <segher at gcc dot gnu.org> ---
The mystery is not where the permutations came from: they were added during
expand to make correct code, just like many unnecessary register moves are
added at that time. This is normal, and even good in many ways.
The question is why they weren't optimised better. This is either due to
some bug, or this is an enhancement request.
next prev parent reply other threads:[~2023-02-28 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 7:52 [Bug target/106770] New: " jens.seifert at de dot ibm.com
2022-08-29 8:16 ` [Bug target/106770] " jens.seifert at de dot ibm.com
2022-08-29 9:57 ` jens.seifert at de dot ibm.com
2023-02-27 16:26 ` segher at gcc dot gnu.org
2023-02-27 17:57 ` jens.seifert at de dot ibm.com
2023-02-27 23:06 ` segher at gcc dot gnu.org
2023-02-28 7:23 ` jens.seifert at de dot ibm.com
2023-02-28 16:57 ` segher at gcc dot gnu.org [this message]
2023-03-02 6:11 ` [Bug target/106770] powerpc64le: " jskumari at gcc dot gnu.org
2023-03-02 7:36 ` jskumari at gcc dot gnu.org
2023-03-02 12:42 ` jskumari at gcc dot gnu.org
2023-03-02 13:26 ` segher at gcc dot gnu.org
2023-03-03 6:02 ` jskumari 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-106770-4-dIHetAcyNR@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).