https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63175
--- Comment #33 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 4 Mar 2015, dje at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63175 > > --- Comment #32 from David Edelsohn <dje at gcc dot gnu.org> --- > "So currently on a tie we don't vectorize basic-blocks (same with GCC 4.8). > That's kind of arbitrary, but given instruction encoding size on x86 for > example > it makes sense." That was just a random comment and not the design decision for that code. If costs are near tie then it becomes quite arbitrary given the very very simple cost modeling of the scalar code. That we choose to keep the scalar code in case the cost model says its equally expensive than the vectorized code is an arbitrary choice. I wonder if in this particular case the vectorized or the scalar version is faster (on ppc)?
