public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [PATCH, rtl-optimization]: Fix PR77452, ICE: in plus_constant, at explow.c
Date: Sun, 04 Sep 2016 14:08:00 -0000	[thread overview]
Message-ID: <CAFULd4ZJ4BKDUSee=PjQc892pDg1uxR+XsUbG4Lw38xi_oBd5Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

Hello!

As shown in the PR [1], combine is able to simplify lowpart
CONST_VECTOR constant pool reference to its inner-mode reference.
However, plus_constant was not able to extract the constant from
narrowed access.

Attached patch teaches plus_constant how to handle this situation.

2016-09-04  Uros Bizjak  <ubizjak@gmail.com>

    PR rtl-optimization/77452
    * explow.c (plus_constant) <case MEM>: Extract scalar constant from
    inner-mode reference to a CONST_VECTOR constant in the constant pool.

2016-09-04  Uros Bizjak  <ubizjak@gmail.com>

testsuite/ChangeLog:

    PR rtl-optimization/77452
    * gcc.target/i386/pr77452.c: New test.

Patch was bootstrapped and regression tested on x86_64-linux-gnu {,-m32}.

OK for mainline and gcc-6 branch?

[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77452

Uros.

[-- Attachment #2: p.diff.txt --]
[-- Type: text/plain, Size: 1441 bytes --]

Index: explow.c
===================================================================
--- explow.c	(revision 239975)
+++ explow.c	(working copy)
@@ -106,7 +106,15 @@ plus_constant (machine_mode mode, rtx x, HOST_WIDE
       if (GET_CODE (XEXP (x, 0)) == SYMBOL_REF
 	  && CONSTANT_POOL_ADDRESS_P (XEXP (x, 0)))
 	{
-	  tem = plus_constant (mode, get_pool_constant (XEXP (x, 0)), c);
+	  rtx cst = get_pool_constant (XEXP (x, 0));
+
+	  if (GET_CODE (cst) == CONST_VECTOR
+	      && GET_MODE_INNER (GET_MODE (cst)) == mode)
+	    {
+	      cst = gen_lowpart (mode, cst);
+	      gcc_assert (cst);
+	    }
+	  tem = plus_constant (mode, cst, c);
 	  tem = force_const_mem (GET_MODE (x), tem);
 	  /* Targets may disallow some constants in the constant pool, thus
 	     force_const_mem may return NULL_RTX.  */
Index: testsuite/gcc.target/i386/pr77452.c
===================================================================
--- testsuite/gcc.target/i386/pr77452.c	(nonexistent)
+++ testsuite/gcc.target/i386/pr77452.c	(working copy)
@@ -0,0 +1,13 @@
+/* { dg-do compile { target int128 } } */
+/* { dg-options "-O -mavx512f -fno-split-wide-types --param max-combine-insns=2" } */
+
+typedef unsigned      int U __attribute__((vector_size(64)));
+typedef unsigned __int128 V __attribute__((vector_size(64)));
+
+V
+foo(V v)
+{
+  v[0] = 1u << ((  ((V)(U){1, 1, v[0]})[0]) & 0xf)
+            >> ((-~((V)(U){1, 1, v[0]})[0]) & 0xf);
+  return v;
+}

             reply	other threads:[~2016-09-04 12:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04 14:08 Uros Bizjak [this message]
2016-09-05 10:34 ` Bernd Schmidt
2016-09-05 11:23   ` Richard Biener

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='CAFULd4ZJ4BKDUSee=PjQc892pDg1uxR+XsUbG4Lw38xi_oBd5Q@mail.gmail.com' \
    --to=ubizjak@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).