From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com, Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH 2/9] rs6000: Remove SPE_CONST_OFFSET_OK
Date: Tue, 13 Jun 2017 12:54:00 -0000 [thread overview]
Message-ID: <2999587f67d6bc40fb5e02d3cd0c21cd998b2481.1497353003.git.segher@kernel.crashing.org> (raw)
In-Reply-To: <cover.1497353003.git.segher@kernel.crashing.org>
In-Reply-To: <cover.1497353003.git.segher@kernel.crashing.org>
2017-06-13 Segher Boessenkool <segher@kernel.crashing.org>
* config/rs6000/rs6000.c (SPE_CONST_OFFSET_OK): Delete.
(rs6000_legitimate_offset_address_p): Return false for anything in
V2SImode or V2SFmode.
---
gcc/config/rs6000/rs6000.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c
index b51ffcc..a1005c0 100644
--- a/gcc/config/rs6000/rs6000.c
+++ b/gcc/config/rs6000/rs6000.c
@@ -8697,9 +8697,6 @@ legitimate_small_data_p (machine_mode mode, rtx x)
&& small_data_operand (x, mode));
}
-/* SPE offset addressing is limited to 5-bits worth of double words. */
-#define SPE_CONST_OFFSET_OK(x) (((x) & ~0xf8) == 0)
-
bool
rs6000_legitimate_offset_address_p (machine_mode mode, rtx x,
bool strict, bool worst_case)
@@ -8728,8 +8725,8 @@ rs6000_legitimate_offset_address_p (machine_mode mode, rtx x,
{
case V2SImode:
case V2SFmode:
- /* SPE vector modes. */
- return SPE_CONST_OFFSET_OK (offset);
+ /* Paired single modes: offset addressing isn't valid. */
+ return false;
case DFmode:
case DDmode:
--
1.9.3
next prev parent reply other threads:[~2017-06-13 12:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 12:53 [PATCH 0/9] rs6000: SPE removal, part 2 Segher Boessenkool
2017-06-13 12:53 ` [PATCH 5/9] rs6000: Updates to t-linux Segher Boessenkool
2017-06-13 13:21 ` David Edelsohn
2017-06-13 12:53 ` [PATCH 1/9] rs6000: Sanitize vector modes Segher Boessenkool
2017-06-13 13:19 ` David Edelsohn
2017-06-13 12:53 ` [PATCH 4/9] rs6000: Remove eabispe.h Segher Boessenkool
2017-06-13 13:21 ` David Edelsohn
2017-06-13 12:53 ` [PATCH 3/9] rs6000: Remove t-spe Segher Boessenkool
2017-06-13 13:20 ` David Edelsohn
2017-06-13 12:54 ` [PATCH 8/9] rs6000: Remove VECTOR_SPE Segher Boessenkool
2017-06-13 13:22 ` David Edelsohn
2017-06-13 12:54 ` [PATCH 6/9] rs6000: Updates to t-rtems Segher Boessenkool
2017-06-13 13:21 ` David Edelsohn
2017-06-13 12:54 ` [PATCH 9/9] rs6000: Comment fixes + some leftovers Segher Boessenkool
2017-06-13 13:23 ` David Edelsohn
2017-06-13 12:54 ` Segher Boessenkool [this message]
2017-06-13 13:20 ` [PATCH 2/9] rs6000: Remove SPE_CONST_OFFSET_OK David Edelsohn
2017-06-13 12:54 ` [PATCH 7/9] rs6000: Remove FIXED_SCRATCH Segher Boessenkool
2017-06-13 13:22 ` David Edelsohn
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=2999587f67d6bc40fb5e02d3cd0c21cd998b2481.1497353003.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.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).