public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] expr: Fix up store_expr into SUBREG_PROMOTED_* target [PR108264]
Date: Tue, 3 Jan 2023 12:02:36 +0100	[thread overview]
Message-ID: <7523997A-401D-45FE-94BF-687C700CBDC4@suse.de> (raw)
In-Reply-To: <Y7QEn3gxmWvMRdr7@tucnak>



> Am 03.01.2023 um 11:34 schrieb Jakub Jelinek via Gcc-patches <gcc-patches@gcc.gnu.org>:
> 
> Hi!
> 
> The following testcase ICEs on s390x-linux (e.g. with -march=z13).
> The problem is that target is (subreg/s/u:SI (reg/v:DI 66 [ x+-4 ]) 4)
> and we call convert_move from temp to the SUBREG_REG of that, expecting
> to extend the value properly.  That works nicely if temp has some
> scalar integer mode (or partial one), but ICEs when temp has V4QImode
> on the assertion that from and to modes have the same bitsize.
> store_expr generally allows say store from V4QI to SI target because
> they have the same size and if temp is a CONST_INT, we already have code
> to convert the constant properly, so the following patch just adds handling
> of non-scalar integer modes by converting them to the mode of target
> first before convert_move extends them.
> 
> Bootstrapped/regtested on x86_64-linux, i686-linux and s390x-linux, ok for
> trunk?

Ok

Richard 

> 2023-01-03  Jakub Jelinek  <jakub@redhat.com>
> 
>    PR middle-end/108264
>    * expr.cc (store_expr): For stores into SUBREG_PROMOTED_* targets
>    from source which doesn't have scalar integral mode first convert
>    it to outer_mode.
> 
>    * gcc.dg/pr108264.c: New test.
> 
> --- gcc/expr.cc.jj    2023-01-02 09:32:23.000000000 +0100
> +++ gcc/expr.cc    2023-01-02 16:48:13.226990815 +0100
> @@ -6226,6 +6226,9 @@ store_expr (tree exp, rtx target, int ca
>      temp = convert_modes (inner_mode, outer_mode, temp,
>                SUBREG_PROMOTED_SIGN (target));
>    }
> +      else if (!SCALAR_INT_MODE_P (GET_MODE (temp)))
> +    temp = convert_modes (outer_mode, TYPE_MODE (TREE_TYPE (exp)),
> +                  temp, SUBREG_PROMOTED_SIGN (target));
> 
>       convert_move (SUBREG_REG (target), temp,
>            SUBREG_PROMOTED_SIGN (target));
> --- gcc/testsuite/gcc.dg/pr108264.c.jj    2023-01-02 17:01:14.865887522 +0100
> +++ gcc/testsuite/gcc.dg/pr108264.c    2023-01-02 17:00:52.238209030 +0100
> @@ -0,0 +1,27 @@
> +/* PR middle-end/108264 */
> +/* { dg-do compile } */
> +/* { dg-options "-O2" } */
> +/* { dg-additional-options "-fpic" { target fpic } } */
> +
> +int v;
> +extern int bar (void);
> +
> +static inline void
> +foo (char *d)
> +{
> +  switch (bar ())
> +    {
> +    case 2:
> +      d[0] = d[1] = d[2] = d[3] = v;
> +      break;
> +    case 4:
> +      d[0] = 0;
> +    }
> +}
> +
> +int
> +baz (int x)
> +{
> +  foo ((char *) &x);
> +  return x;
> +}
> 
>    Jakub
> 

      reply	other threads:[~2023-01-03 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 10:34 Jakub Jelinek
2023-01-03 11:02 ` Richard Biener [this message]

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=7523997A-401D-45FE-94BF-687C700CBDC4@suse.de \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jeffreyalaw@gmail.com \
    /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).