On Thu, Nov 7, 2019 at 5:40 PM Richard Sandiford
wrote:
>
> Richard Biener writes:
> > On Wed, Nov 6, 2019 at 4:58 PM Richard Sandiford
> > wrote:
> >>
> >> Richard Biener writes:
> >> > On Tue, Nov 5, 2019 at 3:27 PM Richard Sandiford
> >> > wrote:
> >> >>
> >> >> vectorizable_assignment hand
Richard Biener writes:
> On Wed, Nov 6, 2019 at 4:58 PM Richard Sandiford
> wrote:
>>
>> Richard Biener writes:
>> > On Tue, Nov 5, 2019 at 3:27 PM Richard Sandiford
>> > wrote:
>> >>
>> >> vectorizable_assignment handles true SSA-to-SSA copies (which hopefully
>> >> we don't see in practice) a
On Wed, Nov 6, 2019 at 4:58 PM Richard Sandiford
wrote:
>
> Richard Biener writes:
> > On Tue, Nov 5, 2019 at 3:27 PM Richard Sandiford
> > wrote:
> >>
> >> vectorizable_assignment handles true SSA-to-SSA copies (which hopefully
> >> we don't see in practice) and no-op conversions that are requi
Richard Biener writes:
> On Tue, Nov 5, 2019 at 3:27 PM Richard Sandiford
> wrote:
>>
>> vectorizable_assignment handles true SSA-to-SSA copies (which hopefully
>> we don't see in practice) and no-op conversions that are required
>> to maintain correct gimple, such as changes between signed and
>
On Tue, Nov 5, 2019 at 3:27 PM Richard Sandiford
wrote:
>
> vectorizable_assignment handles true SSA-to-SSA copies (which hopefully
> we don't see in practice) and no-op conversions that are required
> to maintain correct gimple, such as changes between signed and
> unsigned types. These cases sh
vectorizable_assignment handles true SSA-to-SSA copies (which hopefully
we don't see in practice) and no-op conversions that are required
to maintain correct gimple, such as changes between signed and
unsigned types. These cases shouldn't generate any code and so
shouldn't count against either the