public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/meissner/heads/pr96762)] Do not call LXVL/STXVL on 32-bit. Date: Thu, 27 May 2021 22:15:16 +0000 (GMT) [thread overview] Message-ID: <20210527221516.92976385381D@sourceware.org> (raw) https://gcc.gnu.org/g:3849ea3a3518430708939187659bbcded8cccab2 commit 3849ea3a3518430708939187659bbcded8cccab2 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu May 27 17:27:26 2021 -0400 Do not call LXVL/STXVL on 32-bit. In bug PR target/96762, the code wants to do a block move of a 17 byte string literal in -m32 mode. This involves a shift of the DImode length by 56 bits, which is not available in 32-bit. gcc/ 2021-05-27 Michael Meissner <meissner@linux.ibm.com> PR target/96762 * config/rs6000/rs6000-string.c (expand_block_move): Do not try to do LXVL and STXVL on 32-bit. Diff: --- gcc/config/rs6000/rs6000-string.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/config/rs6000/rs6000-string.c b/gcc/config/rs6000/rs6000-string.c index cc75ca5848e..f3226e25327 100644 --- a/gcc/config/rs6000/rs6000-string.c +++ b/gcc/config/rs6000/rs6000-string.c @@ -2811,7 +2811,7 @@ expand_block_move (rtx operands[], bool might_overlap) gen_func.mov = gen_vsx_movv2di_64bit; } else if (TARGET_BLOCK_OPS_UNALIGNED_VSX - && TARGET_POWER10 && bytes < 16 + && TARGET_POWER10 && bytes < 16 && TARGET_POWERPC64 && orig_bytes > 16 && !(bytes == 1 || bytes == 2 || bytes == 4 || bytes == 8)
next reply other threads:[~2021-05-27 22:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 22:15 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-05-27 21:35 Michael Meissner
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=20210527221516.92976385381D@sourceware.org \ --to=meissner@gcc.gnu.org \ --cc=gcc-cvs@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).