From: Richard Biener <richard.guenther@gmail.com>
To: liuhongt <hongtao.liu@intel.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Michael Meissner <meissner@linux.ibm.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Jim Wilson <jimw@sifive.com>,
Andreas Schwab <schwab@linux-m68k.org>,
Andrew Waterman <andrew@sifive.com>,
asolokha@gmx.com
Subject: Re: [PATCH 2/2] validate_subreg before call gen_lowpart to avoid ICE.
Date: Mon, 13 Sep 2021 08:10:38 +0200 [thread overview]
Message-ID: <CAFiYyc1xoO5vSCr+7grpHjeT_iFnzehs5vy6--JR++a9Cj+6Gw@mail.gmail.com> (raw)
In-Reply-To: <20210910125818.334531-3-hongtao.liu@intel.com>
On Fri, Sep 10, 2021 at 2:58 PM liuhongt <hongtao.liu@intel.com> wrote:
>
> gcc/ChangeLog:
>
> * expmed.c (extract_bit_field_using_extv): validate_subreg
> before call gen_lowpart.
> ---
> gcc/expmed.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/gcc/expmed.c b/gcc/expmed.c
> index 3143f38e057..10d62d857a8 100644
> --- a/gcc/expmed.c
> +++ b/gcc/expmed.c
> @@ -1571,12 +1571,16 @@ extract_bit_field_using_extv (const extraction_insn *extv, rtx op0,
>
> if (GET_MODE (target) != ext_mode)
> {
> + machine_mode tmode = GET_MODE (target);
> /* Don't use LHS paradoxical subreg if explicit truncation is needed
> between the mode of the extraction (word_mode) and the target
> mode. Instead, create a temporary and use convert_move to set
> the target. */
> if (REG_P (target)
> - && TRULY_NOOP_TRUNCATION_MODES_P (GET_MODE (target), ext_mode))
> + && TRULY_NOOP_TRUNCATION_MODES_P (tmode, ext_mode)
> + && validate_subreg (ext_mode, tmode,
> + target,
> + subreg_lowpart_offset (ext_mode, tmode)))
> {
> target = gen_lowpart (ext_mode, target);
That would be equivalent to use gen_lowpart_if_possible?
> if (partial_subreg_p (GET_MODE (spec_target), ext_mode))
> --
> 2.27.0
>
next prev parent reply other threads:[~2021-09-13 6:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 12:58 [PATCH 0/2] Revert r12-3277 since it caused regressions on many other targets liuhongt
2021-09-10 12:58 ` [PATCH 1/2] Revert "Get rid of all float-int special cases in validate_subreg." liuhongt
2021-09-10 13:05 ` Richard Biener
2021-09-10 12:58 ` [PATCH 2/2] validate_subreg before call gen_lowpart to avoid ICE liuhongt
2021-09-10 13:15 ` Richard Biener
2021-09-10 13:27 ` Hongtao Liu
2021-09-10 13:32 ` Richard Biener
2021-09-10 13:44 ` Hongtao Liu
2021-09-10 14:25 ` Hongtao Liu
2021-09-10 21:19 ` Segher Boessenkool
2021-09-11 0:29 ` Hongtao Liu
2021-09-11 1:04 ` Hongtao Liu
2021-09-10 13:52 ` Hongtao Liu
2021-09-10 13:39 ` Hongtao Liu
2021-09-10 13:30 ` Segher Boessenkool
2021-09-10 13:58 ` Richard Biener
2021-09-10 16:24 ` Segher Boessenkool
2021-09-10 18:36 ` Richard Biener
2021-09-10 21:27 ` Segher Boessenkool
2021-09-11 8:25 ` Richard Biener
2021-09-11 9:51 ` Hongtao Liu
2021-09-11 11:09 ` Hongtao Liu
2021-09-13 6:10 ` Richard Biener [this message]
2021-09-13 6:32 ` Hongtao Liu
2021-09-13 9:15 ` Richard Biener
2021-09-13 11:14 ` Hongtao Liu
2021-09-13 11:44 ` Tobias Burnus
2021-09-13 11:45 ` 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=CAFiYyc1xoO5vSCr+7grpHjeT_iFnzehs5vy6--JR++a9Cj+6Gw@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=andrew@sifive.com \
--cc=asolokha@gmx.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=jimw@sifive.com \
--cc=meissner@linux.ibm.com \
--cc=schwab@linux-m68k.org \
--cc=segher@kernel.crashing.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).