On Sat, Nov 21, 2020 at 9:30 PM Jan Hubicka wrote:
>
> > > I tested this by building and running a bunch of workloads for SVE,
> > > with three options:
> > >
> > > (1) -O2
> > > (2) -O2 -ftree-vectorize -fvect-cost-model=very-cheap
> > > (3) -O2 -ftree-vectorize [-fvect-cost-model=cheap]
>
> > I tested this by building and running a bunch of workloads for SVE,
> > with three options:
> >
> > (1) -O2
> > (2) -O2 -ftree-vectorize -fvect-cost-model=very-cheap
> > (3) -O2 -ftree-vectorize [-fvect-cost-model=cheap]
> >
> > All three builds used the default -msve-vector-bits=scalable
On Thu, Nov 19, 2020 at 1:04 PM Richard Sandiford
wrote:
>
> Richard Biener via Gcc-patches writes:
> > On Mon, Nov 16, 2020 at 10:58 AM Richard Sandiford
> > wrote:
> >> > Does the patch also vectorize with SVE loops that have
> >> > unknown loop bound? The documentation isn't entirely
> >> >
Richard Biener via Gcc-patches writes:
> On Mon, Nov 16, 2020 at 10:58 AM Richard Sandiford
> wrote:
>> > Does the patch also vectorize with SVE loops that have
>> > unknown loop bound? The documentation isn't entirely
>> > conclusive there.
>>
>> Yeah, for SVE it vectorises. How about changing
On Mon, Nov 16, 2020 at 10:58 AM Richard Sandiford
wrote:
>
> Richard Biener writes:
> > On Fri, Nov 13, 2020 at 7:35 PM Richard Sandiford via Gcc-patches
> > wrote:
> >>
> >> Currently we have three vector cost models: cheap, dynamic and
> >> unlimited. -O2 -ftree-vectorize uses “cheap” by def
Richard Biener writes:
> On Fri, Nov 13, 2020 at 7:35 PM Richard Sandiford via Gcc-patches
> wrote:
>>
>> Currently we have three vector cost models: cheap, dynamic and
>> unlimited. -O2 -ftree-vectorize uses “cheap” by default, but that's
>> still relatively aggressive about peeling and aliasin
On Fri, Nov 13, 2020 at 7:35 PM Richard Sandiford via Gcc-patches
wrote:
>
> Currently we have three vector cost models: cheap, dynamic and
> unlimited. -O2 -ftree-vectorize uses “cheap” by default, but that's
> still relatively aggressive about peeling and aliasing checks,
> and can lead to sign
Currently we have three vector cost models: cheap, dynamic and
unlimited. -O2 -ftree-vectorize uses “cheap” by default, but that's
still relatively aggressive about peeling and aliasing checks,
and can lead to significant code size growth.
This patch adds an even more conservative choice, which f
