[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 rsandifo at gcc dot gnu.org changed: What|Removed |Added Resolution|--- |FIXED Status|U

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 --- Comment #10 from CVS Commits --- The master branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:4a31a8add56d49867c187d90b3a89e97634543c2 commit r11-1458-g4a31a8add56d49867c187d90b3a89e97634543c2 Author: Kaipeng Zhou Date:

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 --- Comment #9 from Kaipeng Zhou --- Created attachment 48717 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48717&action=edit Remove extra variable created for memory reference in loop vectorization. Looks like no one is preparing this pa

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 --- Comment #8 from Kaipeng Zhou --- (In reply to bin cheng from comment #7) > (In reply to rguent...@suse.de from comment #6) > > On Thu, 21 May 2020, zhoukaipeng3 at huawei dot com wrote: > > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 --- Comment #7 from bin cheng --- (In reply to rguent...@suse.de from comment #6) > On Thu, 21 May 2020, zhoukaipeng3 at huawei dot com wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 > > > > --- Comment #4 from Kaipeng Zhou --

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 --- Comment #6 from rguenther at suse dot de --- On Thu, 21 May 2020, zhoukaipeng3 at huawei dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 > > --- Comment #4 from Kaipeng Zhou --- > Sorry for not expressing clearly. > >

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 --- Comment #5 from bin cheng --- (In reply to Richard Biener from comment #1) > But IVOPTs is supposed to know how to eliminate equal IVs. Maybe it's > confused > about the IFN uses? It's an known issue that IVOPTs has difficulty in recognizin

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 --- Comment #4 from Kaipeng Zhou --- Sorry for not expressing clearly. I have debugged the testcase you provided. Not eliminating them is not caused by IFN. The relevant code is in the "get_computation_aff_1" function. In IVOPTs the IV_STEPs

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 --- Comment #3 from Richard Biener --- Btw, there's already vinfo->ivexpr_map to aid simplifying the IL to a point where IVOPTs can eliminate redundant IVs. Eliminating them in the vectorizer is more complicated because of all the code for the I

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 --- Comment #2 from Kaipeng Zhou --- It seems that IVOPTs has no ability to handle the case where TREE_CODE(iv_step) is SSA_NAME.

[Bug tree-optimization/95199] Remove extra variable created for memory reference in loop vectorization.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95199 Richard Biener changed: What|Removed |Added Keywords||missed-optimization CC|