https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89538
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #8)
> (In reply to Taewook Oh from comment #7)
> > I'm Sorry I was confused about our internal gcc version, and it turns out
> > that the version was 8.3 not 7.3.
> >
> > I downloaded latest 8.3 source and tried it but couldn't repro the problem.
> > Is there a chance that the bug is fixed after the release? Our internal
> > version suggests that it is based on 8.3 around 20180827.
>
> THat is even more confusing, because gcc 8.2.0 has been released on
> 2018-07-26, then the snapshots would declare themselves as 8.2.1, gcc 8.3.0
> has been released on 2019-02-22 and then the snapshots would become 8.3.1.
> So, 8.3 based snapshot from 20180827 is not possible.
I can only confirm that:
commit 75a99965334c6932d813ef3cf536a085901ec7e7 (HEAD)
Author: gccadmin <gccadmin@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Wed Feb 27 00:16:31 2019 +0000
Daily bump.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/gcc-8-branch@269238
138bc75d-0d04-0410-961f-82ee72b054a4
can't expose the vectorization.
As Jakub said, please try to build vanilla GCC and provide which revision you
used to reproduce the problem.
