Richard Biener writes:
>> > [...]
>> > @@ -2898,43 +2899,63 @@ vect_joust_loop_vinfos (loop_vec_info
>> > new_loop_vinfo,
>> >return true;
>> > }
>> >
>> > -/* If LOOP_VINFO is already a main loop, return it unmodified. Otherwise
>> > - try to reanalyze it as a main loop. Return the lo
g of vect_analyze_loop_form. I think I'll put this in
before rewriting the main iteration to first only analyze main
loops (and then possibly unrolled main loops) and only after
settling for the cheapest main loop consider epilogue
vectorization.
As you said the original approach of saving e
Richard Biener writes:
> This refactors the main loop analysis part in vect_analyze_loop,
> re-purposing the existing vect_reanalyze_as_main_loop for this
> to reduce code duplication. Failure flow is a bit tricky since
> we want to extract info from the analyzed loop but I wanted to
> share the
This refactors the main loop analysis part in vect_analyze_loop,
re-purposing the existing vect_reanalyze_as_main_loop for this
to reduce code duplication. Failure flow is a bit tricky since
we want to extract info from the analyzed loop but I wanted to
share the destruction part. Thus I add some
