On October 20, 2019 3:21:32 PM GMT+02:00, Richard Sandiford
wrote:
>Now that we're keeping multiple vec_infos around at the same time,
>it seemed worth turning current_vector_size into a vec_info field.
>This for example simplifies the book-keeping in vect_analyze_loop
>and helps with some follow
Now that we're keeping multiple vec_infos around at the same time,
it seemed worth turning current_vector_size into a vec_info field.
This for example simplifies the book-keeping in vect_analyze_loop
and helps with some follow-on changes.
Tested on aarch64-linux-gnu and x86_64-linux-gnu.
Richard