Richard Biener writes:
>> > So, may I go with the original patch?
>>
>> Still feels like we're counting spills on targets that shouldn't need them.
>> But going back to:
>>
>>/* Assume that a reg-reg move is possible and cheap,
>> do not account for vector to gp register move c
On Wed, 3 Apr 2019, Richard Sandiford wrote:
> Richard Biener writes:
> > On Mon, 1 Apr 2019, Richard Sandiford wrote:
> >
> >> Richard Biener writes:
> >> > This is an update from last years attempt to tame down vectorization
> >> > when it runs in to ABI inefficiencies at function return. I'v
Richard Biener writes:
> On Mon, 1 Apr 2019, Richard Sandiford wrote:
>
>> Richard Biener writes:
>> > This is an update from last years attempt to tame down vectorization
>> > when it runs in to ABI inefficiencies at function return. I've
>> > updated the patch to look for multi-reg returns ins
On Mon, 1 Apr 2019, Richard Sandiford wrote:
> Richard Biener writes:
> > This is an update from last years attempt to tame down vectorization
> > when it runs in to ABI inefficiencies at function return. I've
> > updated the patch to look for multi-reg returns instead of
> > !vector ones (due t
Richard Biener writes:
> This is an update from last years attempt to tame down vectorization
> when it runs in to ABI inefficiencies at function return. I've
> updated the patch to look for multi-reg returns instead of
> !vector ones (due to word_mode vectorization) and handle a bit
> more retur
This is an update from last years attempt to tame down vectorization
when it runs in to ABI inefficiencies at function return. I've
updated the patch to look for multi-reg returns instead of
!vector ones (due to word_mode vectorization) and handle a bit
more returns, esp. the common pattern of
