From: Richard Biener <richard.guenther@gmail.com>
To: YunQiang Su <yunqiang.su@cipunited.com>
Cc: gcc-patches@gcc.gnu.org, pinskia@gmail.com
Subject: Re: [RFC] Store_bit_field_1: Use mode of SUBREG instead of REG
Date: Wed, 12 Jul 2023 09:44:45 +0200 [thread overview]
Message-ID: <CAFiYyc0x=2QH+O43imxebbka1XvnHQrRXyQ-CQLJXyyMVOhTyg@mail.gmail.com> (raw)
In-Reply-To: <20230712031935.3908564-1-yunqiang.su@cipunited.com>
On Wed, Jul 12, 2023 at 5:20 AM YunQiang Su <yunqiang.su@cipunited.com> wrote:
>
> PR #104914
>
> When work with
> int val;
> ((unsigned char*)&val)[0] = *buf;
> The RTX mode is obtained from REG instead of SUBREG,
> which make D<INS> is used instead of <INS>.
> Thus something wrong happens on sign-extend default architectures,
> like MIPS64.
>
> gcc/ChangeLog:
> PR: 104914.
> * expmed.cc(store_bit_field_1): Get mode from original
> str_rtx instead of op0.
> ---
> gcc/expmed.cc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/expmed.cc b/gcc/expmed.cc
> index fbd4ce2d42f..37f90912122 100644
> --- a/gcc/expmed.cc
> +++ b/gcc/expmed.cc
> @@ -849,7 +849,7 @@ store_bit_field_1 (rtx str_rtx, poly_uint64 bitsize, poly_uint64 bitnum,
> if we aren't. This must come after the entire register case above,
> since that case is valid for any mode. The following cases are only
> valid for integral modes. */
> - opt_scalar_int_mode op0_mode = int_mode_for_mode (GET_MODE (op0));
> + opt_scalar_int_mode op0_mode = int_mode_for_mode (GET_MODE (str_rtx));
I don't think this is correct - op0_mode is used to store into op0, and we are
just requiring that it is an integer mode and equal to the original
mode. I suppose
your patch makes us go to the fallback code instead, but it's surely
for the wrong
reason. I also wonder why we don't just check GET_MODE_CLASS
(GET_MODE (op0)) == MODE_CLASS_INT ...
> scalar_int_mode imode;
> if (!op0_mode.exists (&imode) || imode != GET_MODE (op0))
> {
> --
> 2.30.2
>
next prev parent reply other threads:[~2023-07-12 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 3:19 YunQiang Su
2023-07-12 7:44 ` Richard Biener [this message]
2023-07-12 11:22 ` YunQiang Su
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='CAFiYyc0x=2QH+O43imxebbka1XvnHQrRXyQ-CQLJXyyMVOhTyg@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
--cc=yunqiang.su@cipunited.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).