Displaying 7 results from an estimated 7 matches for "loopopt".
Did you mean:
loopops
2017 Mar 08
3
(no subject)
A quick update, we have been looking through all LLVM passes to identify the impact of "IR-region annotation", and interaction issues with the rest of LoopOpt and scalarOpt, e.g. interaction with vectorization when you have schedule(simd:guided: 64). What are the common properties for optimizer to know on IR-region annotations. We have our implementation working from O0, O1, O2 to O3. So far, the changes we made in the existing LLVM opt passes are <...
2017 Mar 08
4
(no subject)
...illinois.edu>; TB Schardl <neboat at mit.edu>; acjacob at us.ibm.com
Subject: Re:
On 03/08, Tian, Xinmin wrote:
> A quick update, we have been looking through all LLVM passes to
> identify the impact of "IR-region annotation", and interaction issues
> with the rest of LoopOpt and scalarOpt, e.g. interaction with
> vectorization when you have schedule(simd:guided: 64). What are the
> common properties for optimizer to know on IR-region annotations. We
> have our implementation working from O0, O1, O2 to O3. So far, the
> changes we made in the existing L...
2017 Mar 08
2
(no subject)
...du>; acjacob at us.ibm.com
>> Subject: Re:
>>
>> On 03/08, Tian, Xinmin wrote:
>>> A quick update, we have been looking through all LLVM passes to
>>> identify the impact of "IR-region annotation", and interaction issues
>>> with the rest of LoopOpt and scalarOpt, e.g. interaction with
>>> vectorization when you have schedule(simd:guided: 64). What are the
>>> common properties for optimizer to know on IR-region annotations. We
>>> have our implementation working from O0, O1, O2 to O3. So far, the
>>> chang...
2017 Mar 08
2
(no subject)
...oat at mit.edu>;
> acjacob at us.ibm.com
> Subject: Re:
>
> On 03/08, Tian, Xinmin wrote:
> > A quick update, we have been looking through all LLVM passes to
> > identify the impact of "IR-region annotation", and interaction
> > issues with the rest of LoopOpt and scalarOpt, e.g. interaction
> > with vectorization when you have schedule(simd:guided: 64). What are
> > the common properties for optimizer to know on IR-region
> > annotations. We have our implementation working from O0, O1, O2 to
> > O3. So far, the changes we ma...
2017 Mar 08
3
[RFC][PIR] Parallel LLVM IR -- Stage 0 --
...>; acjacob at us.ibm.com
>> Subject: Re:
>>
>> On 03/08, Tian, Xinmin wrote:
>>> A quick update, we have been looking through all LLVM passes to
>>> identify the impact of "IR-region annotation", and interaction
>>> issues with the rest of LoopOpt and scalarOpt, e.g. interaction
>>> with vectorization when you have schedule(simd:guided: 64). What are
>>> the common properties for optimizer to know on IR-region
>>> annotations. We have our implementation working from O0, O1, O2 to
>>> O3. So far, the c...
2017 Mar 08
2
[RFC][PIR] Parallel LLVM IR -- Stage 0 --
...bject: Re:
>>>>
>>>> On 03/08, Tian, Xinmin wrote:
>>>>> A quick update, we have been looking through all LLVM passes to
>>>>> identify the impact of "IR-region annotation", and interaction
>>>>> issues with the rest of LoopOpt and scalarOpt, e.g. interaction
>>>>> with vectorization when you have schedule(simd:guided: 64). What are
>>>>> the common properties for optimizer to know on IR-region
>>>>> annotations. We have our implementation working from O0, O1, O2 to
>>&g...
2017 Mar 08
5
(no subject)
<mehdi.amini at apple.com>,
Bcc:
Subject: Re: [llvm-dev] [RFC][PIR] Parallel LLVM IR -- Stage 0 -- IR extension
Reply-To:
In-Reply-To: <20170224221713.GA931 at arch-linux-jd.home>
Ping.
PS.
Are there actually people interested in this?
We will continue working anyway but it might not make sense to put it
on reviews and announce it on the ML if nobody cares.
On 02/24,