search for: elovikov

Displaying 13 results from an estimated 13 matches for "elovikov".

2019 Jun 10
2
[RFC] Expose user provided vector function for auto-vectorization.
...t. Note, that I don't insist on this approach, it's just an alternative to the "hardcoded" usage of OMP's Vector Function ABI. Thanks, Andrei -----Original Message----- From: Francesco Petrogalli <Francesco.Petrogalli at arm.com> Sent: Monday, June 10, 2019 11:38 To: Elovikov, Andrei <andrei.elovikov at intel.com> Cc: llvm-dev at lists.llvm.org; Saito, Hideki <hideki.saito at intel.com> Subject: Re: [RFC] Expose user provided vector function for auto-vectorization. > On Jun 10, 2019, at 1:09 PM, Elovikov, Andrei <andrei.elovikov at intel.com> wro...
2019 Jun 10
2
[RFC] Expose user provided vector function for auto-vectorization.
...e about the tricky processing and we (possibly) will get a somewhat easier to understand IR after the vectorizer. Is that something that might work? Thanks, Andrei -----Original Message----- From: Francesco Petrogalli <Francesco.Petrogalli at arm.com> Sent: Monday, June 10, 2019 09:09 To: Elovikov, Andrei <andrei.elovikov at intel.com> Cc: llvm-dev at lists.llvm.org; Saito, Hideki <hideki.saito at intel.com> Subject: Re: [RFC] Expose user provided vector function for auto-vectorization. Hi Andrei, > On Jun 7, 2019, at 5:46 PM, Elovikov, Andrei <andrei.elovikov at intel.co...
2019 Jun 24
2
RFC: Interface user provided vector functions with the vectorizer.
...t intel.com>; Simon Moll <moll at cs.uni-saarland.de>; LLVM Development List <llvm-dev at lists.llvm.org>; Clang Dev <cfe-dev at lists.llvm.org>; Renato Golin <rengolin at gmail.com>; Finkel, Hal J. <hfinkel at anl.gov>; Andrea Bocci <andrea.bocci at cern.ch>; Elovikov, Andrei <andrei.elovikov at intel.com>; Alexey Bataev <a.bataev at hotmail.com>; nd <nd at arm.com>; Roman Lebedev <lebedev.ri at gmail.com>; Philip Reames <listmail at philipreames.com>; Shawn Landden <slandden at gmail.com> Subject: Re: RFC: Interface user prov...
2019 Jun 24
3
RFC: Interface user provided vector functions with the vectorizer.
> On Jun 24, 2019, at 10:53 AM, Tian, Xinmin <xinmin.tian at intel.com> wrote: > > To me, it is also an issue related to SIMD signature matching when the vectorizer kicks in. Losing info from FE to BE is not good in general. > Yes, we cannot loose such information. In particular, the three examples I reported are all generating i64 in the scalar function signature: // Type 1
2019 Jun 24
4
RFC: Interface user provided vector functions with the vectorizer.
...://aka.ms/ghei36> ________________________________ From: Tian, Xinmin <xinmin.tian at intel.com> Sent: Monday, June 24, 2019 5:28:45 PM To: Saito, Hideki; Francesco Petrogalli; Doerfert, Johannes Cc: Simon Moll; LLVM Development List; Clang Dev; Renato Golin; Finkel, Hal J.; Andrea Bocci; Elovikov, Andrei; Alexey Bataev; nd; Roman Lebedev; Philip Reames; Shawn Landden Subject: RE: RFC: Interface user provided vector functions with the vectorizer. >>>>I don’t know if this is going to be a problem for other architectures ++++++I haven't checked what IA-32/Intel64 should do fo...
2019 Jun 07
2
[RFC] Expose user provided vector function for auto-vectorization.
Hi All, [I'm only subscribed to digest, so the reply doesn't look great, sorry about that] > The second component is a tool that other parts of LLVM (for example, the loop vectorizer) can use to query the availability of the vector function, the SVFS I have described in the original post of the RFC, which is based on interpreting the `vector-variant` attribute. > The final
2019 Jun 24
2
RFC: Interface user provided vector functions with the vectorizer.
...t intel.com>; Simon Moll <moll at cs.uni-saarland.de>; LLVM Development List <llvm-dev at lists.llvm.org>; Clang Dev <cfe-dev at lists.llvm.org>; Renato Golin <rengolin at gmail.com>; Finkel, Hal J. <hfinkel at anl.gov>; Andrea Bocci <andrea.bocci at cern.ch>; Elovikov, Andrei <andrei.elovikov at intel.com>; Alexey Bataev <a.bataev at hotmail.com>; nd <nd at arm.com>; Roman Lebedev <lebedev.ri at gmail.com>; Philip Reames <listmail at philipreames.com>; Shawn Landden <slandden at gmail.com> Subject: Re: RFC: Interface user prov...
2019 Jun 21
2
RFC: Interface user provided vector functions with the vectorizer.
...anl.gov> Cc: Simon Moll <moll at cs.uni-saarland.de>; LLVM Development List <llvm-dev at lists.llvm.org>; Clang Dev <cfe-dev at lists.llvm.org>; Renato Golin <rengolin at gmail.com>; Finkel, Hal J. <hfinkel at anl.gov>; Andrea Bocci <andrea.bocci at cern.ch>; Elovikov, Andrei <andrei.elovikov at intel.com>; Alexey Bataev <a.bataev at hotmail.com>; Saito, Hideki <hideki.saito at intel.com>; Tian, Xinmin <xinmin.tian at intel.com>; nd <nd at arm.com>; Roman Lebedev <lebedev.ri at gmail.com>; Philip Reames <listmail at philipr...
2017 May 16
2
[RFC] Canonicalization of unsigned subtraction with saturation
On 5/16/2017 6:30 AM, Sanjay Patel wrote: > Thanks for posting this question, Julia. > > I had a similar question about a signed min/max variant here: > http://lists.llvm.org/pipermail/llvm-dev/2016-November/106868.html > > The 2nd version in each case contains a canonical max/min > representation in IR, and this could enable more IR analysis. > A secondary advantage is
2017 Dec 06
2
Question about visibility analysis for whole program devirtualization pass
Hi Peter, Thanks for the reply. I agree that the base class vtable may be not referenced by a derived class. However, the vtable of a derived class has to reference its parent type_info, and so having type_info internalized means that the class is final, doesn’t it? Thanks, Nikolai From: Peter Collingbourne [mailto:peter at pcc.me.uk] Sent: Wednesday, December 6, 2017 4:36 AM To: Gainullin,
2019 Jun 17
3
RFC: Interface user provided vector functions with the vectorizer.
...ing on this. Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Simon Moll <moll at cs.uni-saarland.de> Sent: Monday, June 17, 2019 10:02:58 AM To: Francesco Petrogalli; LLVM Development List; Clang Dev Cc: Renato Golin; Finkel, Hal J.; Andrea Bocci; Elovikov, Andrei; Alexey Bataev; Doerfert, Johannes; Saito, Hideki; Tian, Xinmin; nd; Roman Lebedev; Philip Reames; Shawn Landden Subject: Re: RFC: Interface user provided vector functions with the vectorizer. Hi Francesco, On 6/11/19 10:55 PM, Francesco Petrogalli wrote: > Dear all, > > I have r...
2019 Jun 24
2
RFC: Interface user provided vector functions with the vectorizer.
...ng on this. >> >> Get Outlook for Android >> >> From: Simon Moll <moll at cs.uni-saarland.de> >> Sent: Monday, June 17, 2019 10:02:58 AM >> To: Francesco Petrogalli; LLVM Development List; Clang Dev >> Cc: Renato Golin; Finkel, Hal J.; Andrea Bocci; Elovikov, Andrei; > Alexey Bataev; Doerfert, Johannes; Saito, Hideki; Tian, Xinmin; nd; > Roman Lebedev; Philip Reames; Shawn Landden >> Subject: Re: RFC: Interface user provided vector functions with the vectorizer. >> >> Hi Francesco, >> >> On 6/11/19 10:55 PM, Franc...
2019 Jun 11
2
RFC: Interface user provided vector functions with the vectorizer.
Dear all, I have re-written the proposal for interfacing user provided vector functions, originally posted in both llvm-dev and cfe-dev mailing list: "[RFC] Expose user provided vector function for auto-vectorization." The proposal looks quite different from the original submission, therefore I took the liberty to start a new thread. The original thread generated some good