From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] forwprop: Remove incorrect assertion [PR102897]
Date: Tue, 26 Oct 2021 18:08:06 +0800 [thread overview]
Message-ID: <79737851-dd1b-8b57-30a7-e883b6205a58@linux.ibm.com> (raw)
In-Reply-To: <CAFiYyc3MWu7qsnxAwD3aT-2wi3JyRN3WOS4xLVnkqhbfkpCSRQ@mail.gmail.com>
Hi Richi,
on 2021/10/26 下午3:50, Richard Biener wrote:
> On Tue, Oct 26, 2021 at 5:40 AM Kewen.Lin <linkw@linux.ibm.com> wrote:
>>
>> Hi,
>>
>> As PR102897 shows, there is one incorrect assertion in function
>> simplify_permutation, which is based on the wrong assumption that
>> all cases with op2_type == tgt_type are handled previously, the
>> proposed fix is to remove this wrong assertion.
>>
>> Bootstrapped and regtested on x86_64-redhat-linux,
>> aarch64-linux-gnu and powerpc64{,le}-linux-gnu.
>
> I think you need to enable optimization in the new testcase, gcc.dg/ only
> runs -O0 by default which wouldn't trigger forwprop? Please verify the
> testcase ICEs before the fix.
>
Thanks for catching! You are right, the optimization option is required,
I just verified it and committed with the additional "-O1" as r12-4705.
> Otherwise OK.
>
Thanks!
BR,
Kewen
> Thanks,
> Richard,
>
>> BR,
>> Kewen
>> -----
>> gcc/ChangeLog:
>>
>> PR tree-optimization/102897
>> * tree-ssa-forwprop.c (simplify_permutation): Remove a wrong assertion.
>>
>> gcc/testsuite/ChangeLog:
>>
>> * gcc.dg/pr102897.c: New test.
>> ---
>> gcc/testsuite/gcc.dg/pr102897.c | 16 ++++++++++++++++
>> gcc/tree-ssa-forwprop.c | 2 --
>> 2 files changed, 16 insertions(+), 2 deletions(-)
>> create mode 100644 gcc/testsuite/gcc.dg/pr102897.c
>>
>> diff --git a/gcc/testsuite/gcc.dg/pr102897.c b/gcc/testsuite/gcc.dg/pr102897.c
>> new file mode 100644
>> index 00000000000..d96b0e48ccc
>> --- /dev/null
>> +++ b/gcc/testsuite/gcc.dg/pr102897.c
>> @@ -0,0 +1,16 @@
>> +/* { dg-do compile } */
>> +/* Specify C99 to avoid the warning/error on compound literals. */
>> +/* { dg-options "-std=c99" } */
>> +
>> +/* Verify that there is no ICE. */
>> +
>> +typedef __attribute__((vector_size(8))) signed char int8x8_t;
>> +typedef __attribute__((vector_size(8))) unsigned char uint8x8_t;
>> +
>> +int8x8_t fn1 (int8x8_t val20, char tmp)
>> +{
>> + uint8x8_t __trans_tmp_3;
>> + __trans_tmp_3 = (uint8x8_t){tmp};
>> + int8x8_t __a = (int8x8_t) __trans_tmp_3;
>> + return __builtin_shuffle (__a, val20, (uint8x8_t){0});
>> +}
>> diff --git a/gcc/tree-ssa-forwprop.c b/gcc/tree-ssa-forwprop.c
>> index 5b30d4c1a76..a830bab78ba 100644
>> --- a/gcc/tree-ssa-forwprop.c
>> +++ b/gcc/tree-ssa-forwprop.c
>> @@ -2267,8 +2267,6 @@ simplify_permutation (gimple_stmt_iterator *gsi)
>> if (!VECTOR_TYPE_P (tgt_type))
>> return 0;
>> tree op2_type = TREE_TYPE (op2);
>> - /* Should have folded this before. */
>> - gcc_assert (op2_type != tgt_type);
>>
>> /* Figure out the shrunk factor. */
>> poly_uint64 tgt_units = TYPE_VECTOR_SUBPARTS (tgt_type);
>> --
>> 2.27.0
next prev parent reply other threads:[~2021-10-26 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 3:40 Kewen.Lin
2021-10-26 7:50 ` Richard Biener
2021-10-26 10:08 ` Kewen.Lin [this message]
2021-10-27 7:51 ` [committed] testsuite: Fix up gcc.dg/pr102897.c testcase [PR102897] Jakub Jelinek
2021-10-27 9:24 ` Kewen.Lin
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=79737851-dd1b-8b57-30a7-e883b6205a58@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@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).