public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102146] [11 regression] several test cases fails after r11-8940
Date: Tue, 16 Aug 2022 21:24:11 +0000 [thread overview]
Message-ID: <bug-102146-4-ALgtRqPZhc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102146-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102146
--- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Segher Boessenkool
<segher@gcc.gnu.org>:
https://gcc.gnu.org/g:2eb21e7349cda2885438463f045f6729a47039e8
commit r11-10207-g2eb21e7349cda2885438463f045f6729a47039e8
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date: Sun Jan 2 14:08:35 2022 +0000
rs6000: Disparage lfiwzx and similar
RA now chooses GEN_OR_VSX_REGS in most cases. This is great in most
cases, but we often (or always?) use {l,st}{f,xs}iwzx now, which is
problematic because the integer load and store insns can use cheaper
addressing modes. We can fix that by putting a small penalty on the
instruction alternatives for those.
2022-04-21 Segher Boessenkool <segher@kernel.crashing.org>
PR target/103197
PR target/102146
* config/rs6000/rs6000.md (zero_extendqi<mode>2 for EXTQI):
Disparage
the "Z" alternatives in {l,st}{f,xs}iwzx.
(zero_extendhi<mode>2 for EXTHI): Ditto.
(zero_extendsi<mode>2 for EXTSI): Ditto.
(*movsi_internal1): Ditto.
(*mov<mode>_internal1 for QHI): Ditto.
(movsd_hardfloat): Ditto.
(cherry picked from commit 26fa464f42622c60d6929720dd37143a21054ede)
next prev parent reply other threads:[~2022-08-16 21:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 15:11 [Bug target/102146] New: " seurer at gcc dot gnu.org
2021-09-01 8:23 ` [Bug target/102146] " rguenth at gcc dot gnu.org
2021-09-02 8:24 ` guihaoc at gcc dot gnu.org
2022-04-07 8:34 ` rguenth at gcc dot gnu.org
2022-04-07 8:50 ` jakub at gcc dot gnu.org
2022-04-08 1:19 ` guihaoc at gcc dot gnu.org
2022-04-08 1:26 ` guihaoc at gcc dot gnu.org
2022-04-12 0:46 ` aoliva at gcc dot gnu.org
2022-04-13 1:43 ` cvs-commit at gcc dot gnu.org
2022-04-13 7:25 ` rguenth at gcc dot gnu.org
2022-04-14 0:41 ` guihaoc at gcc dot gnu.org
2022-04-14 1:11 ` guihaoc at gcc dot gnu.org
2022-04-21 21:31 ` cvs-commit at gcc dot gnu.org
2022-04-21 21:31 ` cvs-commit at gcc dot gnu.org
2022-05-19 22:13 ` bergner at gcc dot gnu.org
2022-05-19 23:06 ` bergner at gcc dot gnu.org
2022-05-20 0:54 ` guihaoc at gcc dot gnu.org
2022-08-16 21:24 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-16 21:24 ` cvs-commit at gcc dot gnu.org
2022-08-16 23:35 ` cvs-commit at gcc dot gnu.org
2022-08-16 23:40 ` segher at gcc dot gnu.org
2022-08-17 2:20 ` guihaoc at gcc dot gnu.org
2022-08-24 16:58 ` segher at gcc dot gnu.org
2023-04-03 3:15 ` cvs-commit at gcc dot gnu.org
2023-04-18 1:59 ` linkw 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-102146-4-ALgtRqPZhc@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).