public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-9061] match.pd: Fix ICE on BIT_INSERT_EXPR of BIT_FIELD_REF folding [PR113967]
Date: Mon, 19 Feb 2024 08:45:09 +0000 (GMT)	[thread overview]
Message-ID: <20240219084509.44C3A386186F@sourceware.org> (raw)

https://gcc.gnu.org/g:2bfdeca19d96239479488cd07b1e952d95a02f72

commit r14-9061-g2bfdeca19d96239479488cd07b1e952d95a02f72
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Feb 19 09:42:22 2024 +0100

    match.pd: Fix ICE on BIT_INSERT_EXPR of BIT_FIELD_REF folding [PR113967]
    
    The following testcase ICEs, because BIT_FIELD_REF's position is not
    multiple of the vector element's bit size and the code uses exact_div
    to divide those 2 values.
    
    For BIT_INSERT_EXPR, the tree-cfg.cc verification verifies the position
    is a multiple of the inserted bit size when inserting into vectors,
    but for BIT_FIELD_REF the position can be arbitrary if within the range.
    
    The following patch fixes that.
    
    2024-02-19  Jakub Jelinek  <jakub@redhat.com>
    
            PR tree-optimization/113967
            * match.pd (bit_insert @0 (BIT_FIELD_REF @1 ..) ..): Require
            in condition that @rpos is multiple of vector element size.
    
            * gcc.dg/pr113967.c: New test.

Diff:
---
 gcc/match.pd                    |  4 +++-
 gcc/testsuite/gcc.dg/pr113967.c | 14 ++++++++++++++
 2 files changed, 17 insertions(+), 1 deletion(-)

diff --git a/gcc/match.pd b/gcc/match.pd
index 711c3a10c3ff..c5b6540f939a 100644
--- a/gcc/match.pd
+++ b/gcc/match.pd
@@ -8586,7 +8586,9 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
 	  || optimize_vectors_before_lowering_p ())
       && types_match (@0, @1)
       && types_match (TREE_TYPE (TREE_TYPE (@0)), TREE_TYPE (@2))
-      && TYPE_VECTOR_SUBPARTS (type).is_constant ())
+      && TYPE_VECTOR_SUBPARTS (type).is_constant ()
+      && multiple_p (wi::to_poly_offset (@rpos),
+		     wi::to_poly_offset (TYPE_SIZE (TREE_TYPE (type)))))
   (with
    {
      unsigned HOST_WIDE_INT elsz
diff --git a/gcc/testsuite/gcc.dg/pr113967.c b/gcc/testsuite/gcc.dg/pr113967.c
new file mode 100644
index 000000000000..21621809564b
--- /dev/null
+++ b/gcc/testsuite/gcc.dg/pr113967.c
@@ -0,0 +1,14 @@
+/* PR tree-optimization/113967 */
+/* { dg-do compile } */
+/* { dg-options "-O2" } */
+
+typedef unsigned short W __attribute__((vector_size (4 * sizeof (short))));
+
+void
+foo (W *p)
+{
+  W x = *p;
+  W y = {};
+  __builtin_memcpy (&y, 1 + (char *) &x, sizeof (short));
+  *p = y;
+}

                 reply	other threads:[~2024-02-19  8:45 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=20240219084509.44C3A386186F@sourceware.org \
    --to=jakub@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: 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).