From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: [PATCH] vect: Move suggested_unroll_factor applying [PR105940]
Date: Tue, 14 Jun 2022 14:03:32 +0800 [thread overview]
Message-ID: <58789880-1e02-15fb-9ff0-f354312de2a1@linux.ibm.com> (raw)
In-Reply-To: <CAFiYyc0a6t-3_HsJ3gak1wZbF6jcUV6WNUSmok7Gim6tsz3Cuw@mail.gmail.com>
on 2022/6/13 19:38, Richard Biener wrote:
> On Mon, Jun 13, 2022 at 12:02 PM Kewen.Lin <linkw@linux.ibm.com> wrote:
>>
>> Hi,
>>
>> As PR105940 shown, when rs6000 port tries to assign
>> m_suggested_unroll_factor by 4 or so, there will be ICE
>> on below statement:
>>
>> exact_div (LOOP_VINFO_VECT_FACTOR (loop_vinfo),
>> loop_vinfo->suggested_unroll_factor);
>>
>> In function vect_analyze_loop_2, the current place of
>> suggested_unroll_factor applying can't guarantee it's
>> applied for all cases. As the case shows, vectorizer
>> could retry with SLP forced off, the vf is reset by
>> saved_vectorization_factor which isn't applied with
>> suggested_unroll_factor before. It means it can end
>> up with one vf which neglects suggested_unroll_factor.
>> I think it's off design, we should move the applying
>> of suggested_unroll_factor after start_over.
>>
>> Bootstrapped and regtested on x86_64-redhat-linux,
>> aarch64-linux-gnu and powerpc64{,le}-linux-gnu.
>>
>> Is it ok for trunk?
>
> OK (I think the GCC 12 branch is also affected).
>
Thanks Richi! Committed as r13-1083.
I'll backport this to GCC12 branch in a week if it goes well in trunk.
BR,
Kewen
prev parent reply other threads:[~2022-06-14 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 10:02 Kewen.Lin
2022-06-13 11:38 ` Richard Biener
2022-06-14 6:03 ` Kewen.Lin [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=58789880-1e02-15fb-9ff0-f354312de2a1@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.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).