public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98799] [10 Regression] vector_set_var ICE
Date: Sat, 23 Jan 2021 20:00:38 +0000	[thread overview]
Message-ID: <bug-98799-4-JiDPWgxLdK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98799-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98799

--- Comment #2 from David Edelsohn <dje at gcc dot gnu.org> ---
As with vector_extract, the P8 version requires TARGET_DIRECT_MOVE_64BIT.

I think that this needs something like the following:

--- rs6000.c    2021-01-22 11:45:39.000000000 -0500
+++ cc.c        2021-01-23 14:55:25.000000000 -0500
@@ -6993,9 +6993,14 @@ rs6000_expand_vector_set (rtx target, rt

   if (VECTOR_MEM_VSX_P (mode))
     {
-      if (!CONST_INT_P (elt_rtx))
+      if (!CONST_INT_P (elt_rtx)
+         && (TARGET_P9_VECTOR || TARGET_DIRECT_MOVE_64BIT))
        {
-         rs6000_expand_vector_set_var (target, val, elt_rtx);
+         if (TARGET_P9_VECTOR
+             || GET_MODE_SIZE (GET_MODE_INNER (GET_MODE (target))) == 8)
+           rs6000_expand_vector_set_var_p9 (target, val, idx);
+         else
+           rs6000_expand_vector_set_var_p8 (target, val, idx);
          return;
        }

@@ -7235,19 +7240,6 @@
     gen_vector_select_v16qi (target_v16qi, target_v16qi, val_perm,
mask_perm));
 }

-/* Insert VAL into IDX of TARGET, VAL size is same of the vector element, IDX
-   is variable and also counts by vector element size.  */
-
-void
-rs6000_expand_vector_set_var (rtx target, rtx val, rtx idx)
-{
-  machine_mode mode = GET_MODE (target);
-  machine_mode inner_mode = GET_MODE_INNER (mode);
-  if (TARGET_P9_VECTOR || GET_MODE_SIZE (inner_mode) == 8)
-    rs6000_expand_vector_set_var_p9 (target, val, idx);
-  else
-    rs6000_expand_vector_set_var_p8 (target, val, idx);
-}

 /* Extract field ELT from VEC into TARGET.  */


I also don't see the purpose of rs6000_expand_vector_set_var() helper function,
especially not as a global function.

  parent reply	other threads:[~2021-01-23 20:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 20:15 [Bug target/98799] New: " dje at gcc dot gnu.org
2021-01-22 20:17 ` [Bug target/98799] " dje at gcc dot gnu.org
2021-01-23 20:00 ` dje at gcc dot gnu.org [this message]
2021-01-23 22:58 ` dje at gcc dot gnu.org
2021-01-24  2:25 ` dje at gcc dot gnu.org
2021-01-25  8:15 ` luoxhu at gcc dot gnu.org
2021-01-28  3:35 ` [Bug target/98799] [11 " cvs-commit at gcc dot gnu.org
2021-01-29  1:36 ` luoxhu 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-98799-4-JiDPWgxLdK@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).