https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
--- Comment #5 from rguenther at suse dot de ---
On Mon, 8 Jan 2018, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
>
> --- Comment #4 from Jakub Jelinek ---
> Before store-merging we have:
> MEM[(int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
--- Comment #4 from Jakub Jelinek ---
Before store-merging we have:
MEM[(int *)] = { 5, 4, 3, 2 };
t_2 = arr[0];
_65 = arr[1];
_69 = arr[2];
_73 = arr[3];
arr[0] = _69;
arr[1] = _73;
arr[2] = 1;
arr[3] = t_2;
vect__2.5_38 =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
--- Comment #3 from Richard Biener ---
Yes, it's not really sth new but a known issue with late value-numbering. Note
that FRE wouldn't know how to simplify this either, we'd need store-merging
to effectively vectorize the earlier sets. BB
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Known to work|
