From: Richard Biener <richard.guenther@gmail.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Robin Dapp <rdapp@linux.ibm.com>
Subject: Re: [PATCH] Fix typo in gimple_fold_partial_load_store_mem_ref
Date: Wed, 16 Nov 2022 16:36:33 +0100 [thread overview]
Message-ID: <CAFiYyc2OCunNTfSTfnF-YbRwoF3HddBBwJtZHfp9FVftRvSbiQ@mail.gmail.com> (raw)
In-Reply-To: <f1d78b22-e5e9-5104-a3aa-750d8bb6cba2@linux.ibm.com>
On Wed, Nov 16, 2022 at 8:29 AM Kewen.Lin <linkw@linux.ibm.com> wrote:
>
> Hi,
>
> As Robin spotted, my recent commit r13-3716 caused an ICE
> on s390 if vector access with length is enabled there (his
> patch for the enablement hasn't been committed yet). The
> failure is caused by one stupid typo, the bias on s390 is
> -1, so the assertion should use tree_fits_shwi_p rather
> than tree_fits_uhwi_p. Thanks for Robin's catching.
>
> I just reproduced the ICE and verified the fix worked fine
> with a cross build, the optimized dump against the test case
> gcc.target/powerpc/pr107412.c looked expected.
>
> Is it ok for trunk?
OK.
> BR,
> Kewen
> -----
> gcc/ChangeLog:
>
> * gimple-fold.cc (gimple_fold_partial_load_store_mem_ref): Use
> tree_fits_shwi_p rather than tree_fits_uhwi_p as bias is signed.
> ---
> gcc/gimple-fold.cc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/gimple-fold.cc b/gcc/gimple-fold.cc
> index 0a212e6d0d4..f8a1875ea3e 100644
> --- a/gcc/gimple-fold.cc
> +++ b/gcc/gimple-fold.cc
> @@ -5392,7 +5392,7 @@ gimple_fold_partial_load_store_mem_ref (gcall *call, tree vectype, bool mask_p)
> return NULL_TREE;
> unsigned int nargs = gimple_call_num_args (call);
> tree bias = gimple_call_arg (call, nargs - 1);
> - gcc_assert (tree_fits_uhwi_p (bias));
> + gcc_assert (tree_fits_shwi_p (bias));
> tree biased_len = int_const_binop (MINUS_EXPR, basic_len, bias);
> unsigned int len = tree_to_uhwi (biased_len);
> unsigned int vect_len
> --
> 2.25.1
prev parent reply other threads:[~2022-11-16 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 7:29 Kewen.Lin
2022-11-16 15:36 ` 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=CAFiYyc2OCunNTfSTfnF-YbRwoF3HddBBwJtZHfp9FVftRvSbiQ@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=rdapp@linux.ibm.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).