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/103197] ppc inline expansion of memcpy/memmove should not use lxsibzx/stxsibx for a single byte Date: Thu, 21 Apr 2022 21:31:20 +0000 [thread overview] Message-ID: <bug-103197-4-p7lmlqBbVi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103197-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103197 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Segher Boessenkool <segher@gcc.gnu.org>: https://gcc.gnu.org/g:26fa464f42622c60d6929720dd37143a21054ede commit r12-8221-g26fa464f42622c60d6929720dd37143a21054ede 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.
next prev parent reply other threads:[~2022-04-21 21:31 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-11 18:27 [Bug target/103197] New: " acsawdey at gcc dot gnu.org 2021-11-11 18:46 ` [Bug target/103197] " acsawdey at gcc dot gnu.org 2021-11-11 19:36 ` acsawdey at gcc dot gnu.org 2021-11-12 11:19 ` segher at gcc dot gnu.org 2021-11-15 16:02 ` acsawdey at gcc dot gnu.org 2021-11-16 16:40 ` acsawdey at gcc dot gnu.org 2021-11-17 21:40 ` segher at gcc dot gnu.org 2021-11-18 1:31 ` amodra at gmail dot com 2021-11-18 18:11 ` segher at gcc dot gnu.org 2022-01-05 18:15 ` segher at gcc dot gnu.org 2022-01-05 18:18 ` segher at gcc dot gnu.org 2022-01-17 5:51 ` guihaoc at gcc dot gnu.org 2022-02-04 1:51 ` segher at gcc dot gnu.org 2022-04-21 21:31 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-21 21:31 ` cvs-commit at gcc dot gnu.org 2022-08-16 21:24 ` [Bug target/103197] [10/11] " cvs-commit at gcc dot gnu.org 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:38 ` segher 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-103197-4-p7lmlqBbVi@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: linkBe 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).