search for: getannotatedvectorsafelen

> I recommend that you send patches for an implementation > (including the Loop::GetAnnotatedVectorSafelen function > and associated updates to the vectorizer) for review. I expect to send the patches for review later this week. > Make sure to remember LangRef updates! Thanks for the reminder. > Also, looking at the original proposal again, I see no reason > to restrict this to an i3...

----- Original Message ----- > From: "Roel Jordans" <r.jordans at tue.nl> > To: llvmdev at cs.uiuc.edu > Sent: Wednesday, August 13, 2014 5:57:15 AM > Subject: Re: [LLVMdev] Proposal for ""llvm.mem.vectorize.safelen" > > > > > WHY CURRENT METADATA DOES NOT SUFFICE > > ------------------------------------- > > > > There

...Proposal for ""llvm.mem.vectorize.safelen" Message-ID: <51C2718BFE68DA4698E41A5C59B2BB69574200FB at fmsmsx116.amr.corp.intel.com> Content-Type: text/plain; charset="utf-8" > I recommend that you send patches for an implementation > (including the Loop::GetAnnotatedVectorSafelen function > and associated updates to the vectorizer) for review. I expect to send the patches for review later this week. > Make sure to remember LangRef updates! Thanks for the reminder. > Also, looking at the original proposal again, I see no reason > to restrict this to an i32:...

On 12 August 2014 18:49, Johannes Doerfert <doerfert at cs.uni-saarland.de> wrote: > I recently submitted a patch to the list [1] which would allow Polly to > extract the dependency distance for each analyzable loop. While the > distance is often not constant but parametric we would also need to > version the vectorized loop based on the actual runtime values. Since this is a

....vectorize.safelen" > Message-ID: > <51C2718BFE68DA4698E41A5C59B2BB69574200FB at fmsmsx116.amr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > > I recommend that you send patches for an implementation > > (including the Loop::GetAnnotatedVectorSafelen function > > and associated updates to the vectorizer) for review. > > I expect to send the patches for review later this week. > > > Make sure to remember LangRef updates! > > Thanks for the reminder. > > > Also, looking at the original proposal again, I see no...

...Message-ID: > > <51C2718BFE68DA4698E41A5C59B2BB69574200FB at fmsmsx116.amr.corp.intel.com> > > > > Content-Type: text/plain; charset="utf-8" > > > > > I recommend that you send patches for an implementation > > > (including the Loop::GetAnnotatedVectorSafelen function > > > and associated updates to the vectorizer) for review. > > > > I expect to send the patches for review later this week. > > > > > Make sure to remember LangRef updates! > > > > Thanks for the reminder. > > > > > Also, loo...

On 08/20, Arnold Schwaighofer wrote: > > > On Aug 20, 2014, at 8:08 AM, Robison, Arch <arch.robison at intel.com> wrote: > > > >> I recommend that you send patches for an implementation > >> (including the Loop::GetAnnotatedVectorSafelen function > >> and associated updates to the vectorizer) for review. > > > > I expect to send the patches for review later this week. > > > >> Make sure to remember LangRef updates! > > > > Thanks for the reminder. > > > >> Also, l...

...<51C2718BFE68DA4698E41A5C59B2BB69574200FB at fmsmsx116.amr.corp.intel.com> > > > > > > Content-Type: text/plain; charset="utf-8" > > > > > > > I recommend that you send patches for an implementation > > > > (including the Loop::GetAnnotatedVectorSafelen function > > > > and associated updates to the vectorizer) for review. > > > > > > I expect to send the patches for review later this week. > > > > > > > Make sure to remember LangRef updates! > > > > > > Thanks for the reminder....