Re: [38/46] Pass stmt_vec_infos instead of data_references where relevant

On Thu, Jul 26, 2018 at 1:05 PM Richard Sandiford wrote: > > Richard Sandiford writes: > > Richard Biener writes: > >> On Tue, Jul 24, 2018 at 12:08 PM Richard Sandiford > >> wrote: > >>> > >>> This patch makes various routines (mostly in tree-vect-data-refs.c) > >>> take stmt_vec_infos rather

Re: [38/46] Pass stmt_vec_infos instead of data_references where relevant

Richard Sandiford writes: > Richard Biener writes: >> On Tue, Jul 24, 2018 at 12:08 PM Richard Sandiford >> wrote: >>> >>> This patch makes various routines (mostly in tree-vect-data-refs.c) >>> take stmt_vec_infos rather than data_references. The affected routines >>> are really dealing with t

Re: [38/46] Pass stmt_vec_infos instead of data_references where relevant

Richard Biener writes: > On Tue, Jul 24, 2018 at 12:08 PM Richard Sandiford > wrote: >> >> This patch makes various routines (mostly in tree-vect-data-refs.c) >> take stmt_vec_infos rather than data_references. The affected routines >> are really dealing with the way that an access is going to v

Re: [38/46] Pass stmt_vec_infos instead of data_references where relevant

On Tue, Jul 24, 2018 at 12:08 PM Richard Sandiford wrote: > > This patch makes various routines (mostly in tree-vect-data-refs.c) > take stmt_vec_infos rather than data_references. The affected routines > are really dealing with the way that an access is going to vectorised > for a particular stm

[38/46] Pass stmt_vec_infos instead of data_references where relevant

This patch makes various routines (mostly in tree-vect-data-refs.c) take stmt_vec_infos rather than data_references. The affected routines are really dealing with the way that an access is going to vectorised for a particular stmt_vec_info, rather than with the original scalar access described by