search for: rapaport

...Golin [mailto:renato.golin at linaro.org] Sent: Monday, October 16, 2017 4:59 AM To: Hal Finkel <hfinkel at anl.gov> Cc: Daniel Berlin <dberlin at dberlin.org>; Michael Kruse <llvmdev at meinersbur.de>; llvm-dev at lists.llvm.org; Saito, Hideki <hideki.saito at intel.com>; Rapaport, Gil <gil.rapaport at intel.com>; Zaks, Ayal <ayal.zaks at intel.com> Subject: Re: [llvm-dev] [RFC] Polly Status and Integration On 15 October 2017 at 00:57, Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I think the way that we generally look at this is: Our IR...

...model the vectorized code and drive its transformation)   "Extending LoopVectorizer: OpenMP4.5 SIMD and Outer Loop Auto-Vectorization"  (Saito, et.al.) 2016 LLVM Developers' Meeting https://www.youtube.com/watch?v=XXAvdUwO7kQ   "Introducing VPlan to the LoopVectorizer"     (Rapaport and Zaks) 2017 EuroLLVM Developers' Meeting https://www.youtube.com/watch?v=IqzJRs6tb7Y "Vectorizing Loops with VPlan - Current State and Next Steps"   (Zaks and Rapaport) 2017 LLVM Developers' Meeting https://www.youtube.com/watch?v=BjBSJFzYDVk   Patches Committed: --------------...

...ing Loops with VPlan - Current State and Next Steps) Please also refer to the separately sent out status update http://lists.llvm.org/pipermail/llvm-dev/2017-December/119522.html. .   So far, two big patches related to VPlan implementation have been committed. https://reviews.llvm.org/D28975 by Gil Rapaport. (Introducing VPlan to model the vectorized code and drive its transformation)      Has been broken down to a series of smaller patches and went in. The last (re)commit of the series is      https://reviews.llvm.org/rL311849 https://reviews.llvm.org/D38676 by Gil Rapaport. (Modeling masking in VPla...

...- Current State and Next Steps) Please also refer to the separately sent out status update http://lists.llvm.org/pipermail/llvm-dev/2017-December/119522.html. > . > > So far, two big patches related to VPlan implementation have been committed. > https://reviews.llvm.org/D28975 by Gil Rapaport. (Introducing VPlan to > model the vectorized code and drive its transformation) >      Has been broken down to a series of smaller patches and went in. > The last (re)commit of the series is >      https://reviews.llvm.org/rL311849 > https://reviews.llvm.org/D38676 by Gil Rapapo...

...nd Next Steps) Please also refer to the separately sent out status update http://lists.llvm.org/pipermail/llvm-dev/2017-December/119522.html. >> . >> >> So far, two big patches related to VPlan implementation have been committed. >> https://reviews.llvm.org/D28975 by Gil Rapaport. (Introducing VPlan to >> model the vectorized code and drive its transformation) >>      Has been broken down to a series of smaller patches and went in. >> The last (re)commit of the series is >>      https://reviews.llvm.org/rL311849 >> https://reviews.llvm.org/...

On 10/14/2017 05:28 PM, Daniel Berlin via llvm-dev wrote: > > > On Sat, Oct 14, 2017 at 2:54 PM, Michael Kruse <llvmdev at meinersbur.de > <mailto:llvmdev at meinersbur.de>> wrote: > > 2017-10-14 5:03 GMT+02:00 Daniel Berlin <dberlin at dberlin.org > <mailto:dberlin at dberlin.org>>: > > FWIW: We hit a subset of this issue with

...> to the separately sent out status update >>> http://lists.llvm.org/pipermail/llvm-dev/2017-December/119522.html. >>> . >>>    So far, two big patches related to VPlan implementation have been >>> committed. >>> https://reviews.llvm.org/D28975 by Gil Rapaport. (Introducing VPlan to >>> model the vectorized code and drive its transformation) >>>        Has been broken down to a series of smaller patches and went in. >>> The last (re)commit of the series is >>>        https://reviews.llvm.org/rL311849 >>> https...