From: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH, rs6000] Remove redundant logic from rs6000_secondary_reload_direct_move
Date: Tue, 10 Nov 2015 21:04:00 -0000 [thread overview]
Message-ID: <1447189445.5668.4.camel@oc8801110288.ibm.com> (raw)
Hi,
While investigating another issue, I observed some repeated logic in
rs6000_secondary_reload_direct_move (). This patch takes it out. No
functional change intended, and quite straightforward, so I'll plan to
commit shortly if no concerns are raised.
Bootstrapped and tested on powerpc64le-linux-gnu with no regressions.
Thanks,
Bill
2015-11-10 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
* config/rs6000/rs6000.c (rs6000_secondary_reload_direct_move):
Remove redundant code.
Index: gcc/config/rs6000/rs6000.c
===================================================================
--- gcc/config/rs6000/rs6000.c (revision 230052)
+++ gcc/config/rs6000/rs6000.c (working copy)
@@ -17926,29 +17926,8 @@ rs6000_secondary_reload_direct_move (enum rs6000_r
}
}
- if (TARGET_POWERPC64 && size == 16)
+ else if (size == 8)
{
- /* Handle moving 128-bit values from GPRs to VSX point registers on
- power8 when running in 64-bit mode using XXPERMDI to glue the two
- 64-bit values back together. */
- if (to_type == VSX_REG_TYPE && from_type == GPR_REG_TYPE)
- {
- cost = 3; /* 2 mtvsrd's, 1 xxpermdi. */
- icode = reg_addr[mode].reload_vsx_gpr;
- }
-
- /* Handle moving 128-bit values from VSX point registers to GPRs on
- power8 when running in 64-bit mode using XXPERMDI to get access to the
- bottom 64-bit value. */
- else if (to_type == GPR_REG_TYPE && from_type == VSX_REG_TYPE)
- {
- cost = 3; /* 2 mfvsrd's, 1 xxpermdi. */
- icode = reg_addr[mode].reload_gpr_vsx;
- }
- }
-
- else if (!TARGET_POWERPC64 && size == 8)
- {
/* Handle moving 64-bit values from GPRs to floating point registers on
power8 when running in 32-bit mode using FMRGOW to glue the two 32-bit
values back together. Altivec register classes must be handled
reply other threads:[~2015-11-10 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1447189445.5668.4.camel@oc8801110288.ibm.com \
--to=wschmidt@linux.vnet.ibm.com \
--cc=gcc-patches@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).