Displaying 10 results from an estimated 10 matches for "pollyopt".
2013 Aug 09
0
[LLVMdev] [Polly] Summary of some expensive compiler passes, especially PollyDependence
...slightly confused. What are we comparing here? It seems we compare
>> a PollyScopInfo run with a PollyDependences run (same source code?) and
>> the Dependences run shows compile time speedup over ScopInfo? This is
>> surprising.
>
> In fact, there are three runs:
>
> pollyOpt (run id = 18): the baseline of Polly
> pollyScopInfo (run id = 25): Polly with the ScopInfo patch r187728 that split start value from SCEVAddRecExpr
> pollyDependence (run id = 26): Polly with both ScopInfo patch r187728 and PollyDependence patch r187981 that simplify the Read/Write/MayWrite...
2013 Aug 09
2
[LLVMdev] [Polly] Summary of some expensive compiler passes, especially PollyDependence
...&baseline=25
>
>I am slightly confused. What are we comparing here? It seems we compare
>a PollyScopInfo run with a PollyDependences run (same source code?) and
>the Dependences run shows compile time speedup over ScopInfo? This is
>surprising.
In fact, there are three runs:
pollyOpt (run id = 18): the baseline of Polly
pollyScopInfo (run id = 25): Polly with the ScopInfo patch r187728 that split start value from SCEVAddRecExpr
pollyDependence (run id = 26): Polly with both ScopInfo patch r187728 and PollyDependence patch r187981 that simplify the Read/Write/MayWrite before fe...
2013 Aug 11
2
[LLVMdev] [FastPolly]: Update of Polly's performance on LLVM test-suite
...sts and each test is run with 10 samples:
clang (run id = 27): clang -O3
pollyBasic (run id = 28): clang -O3 -load LLVMPolly.so
pollyNoGen (run id = 29): pollycc -O3 -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none
pollyNoOpt (run id = 30): pollycc -O3 -mllvm -polly-optimizer=none
pollyOpt (run id = 31): pollycc -O3
Here is the performance comparison for the newest Polly:
http://188.40.87.11:8000/db_default/v4/nts/31?compare_to=18&baseline=18
Overall, there are 198 benchmarks improved and 16 benchmarks regressed. Especially, with those recent performance-oriented patch fil...
2013 Aug 11
0
[LLVMdev] [FastPolly]: Update of Polly's performance on LLVM test-suite
...with 10 samples:
> clang (run id = 27): clang -O3
> pollyBasic (run id = 28): clang -O3 -load LLVMPolly.so
> pollyNoGen (run id = 29): pollycc -O3 -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none
> pollyNoOpt (run id = 30): pollycc -O3 -mllvm -polly-optimizer=none
> pollyOpt (run id = 31): pollycc -O3
>
>
> Here is the performance comparison for the newest Polly:
> http://188.40.87.11:8000/db_default/v4/nts/31?compare_to=18&baseline=18
It seems the machine is down/unreachable at the moment?
> Overall, there are 198 benchmarks improved and 1...
2013 Aug 09
0
[LLVMdev] [Polly] Summary of some expensive compiler passes, especially PollyDependence
On 08/08/2013 06:27 PM, Star Tan wrote:
> At 2013-08-08 22:28:33,"Tobias Grosser" <tobias at grosser.es> wrote:
>> On 08/08/2013 01:29 AM, Star Tan wrote:
>>> Hi all,
>>>
>>>
>>> I have summarized the top 10 compiler passes for Polly when compiling LLVM test-ssuite. Results can be viewed on:
>>>
2013 Aug 12
1
[LLVMdev] [FastPolly]: Update of Polly's performance on LLVM test-suite
...;> clang (run id = 27): clang -O3
>> pollyBasic (run id = 28): clang -O3 -load LLVMPolly.so
>> pollyNoGen (run id = 29): pollycc -O3 -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none
>> pollyNoOpt (run id = 30): pollycc -O3 -mllvm -polly-optimizer=none
>> pollyOpt (run id = 31): pollycc -O3
> >
>>
>> Here is the performance comparison for the newest Polly:
>> http://188.40.87.11:8000/db_default/v4/nts/31?compare_to=18&baseline=18
>
>It seems the machine is down/unreachable at the moment?
I restart the LNT server. It...
2013 Aug 09
2
[LLVMdev] [Polly] Summary of some expensive compiler passes, especially PollyDependence
...shared object file is very small (usually less than 1%). Their overhead can be viewed on:
http://188.40.87.11:8000/db_default/v4/nts/15?compare_to=14&baseline=14
>> we can see Polly's compile-time overhead is mainly resulted by some expensive Polly passes such as PollyDependence, PollyOptimization and PollyCodegen. Especially, I notice that the PollyDependence can lead to significant extra compile-time overhead. Its compile-time percentage for some expensive benchmarks can be summarized as:
>> nestedloop: 41.4% (Polly - Calculate dependence)
>> salsa20: ...
2013 Sep 17
4
[LLVMdev] [Polly] Compile-time and Execution-time analysis for the SCEV canonicalization
...ption with pNoOptSCEV but replace the LLVMPolly.so by removing all Polly canonicalization passes
pOptSCEV_procomb (run 52): same option with pNoOptSCEV but replace the LLVMPolly.so by removing only the "InstructionCombining" and "PromoteMemoryToRegister" canonicalization passes
pollyOpt (run 53): clang -O3 -load LLVMPolly.so -mllvm -polly
Discovery 1: Polly optimization and code generation heavily relies on the "InstructionCombining" and "PromoteMemoryToRegister" canonicalization passes.
http://188.40.87.11:8000/db_default/v4/nts/52?compare_to=45&baseline...
2013 Sep 14
0
[LLVMdev] [Polly] Compile-time and Execution-time analysis for the SCEV canonicalization
Hello all,
I have evaluated the compile-time and execution-time performance of Polly canonicalization passes. Details can be referred to http://188.40.87.11:8000/db_default/v4/nts/recent_activity. There are four runs:
pollyBasic (run 45): clang -O3 -Xclang -load -Xclang LLVMPolly.so
pollyNoGenSCEV (run 44): clang -O3 -Xclang -load -Xclang LLVMPolly.so -mllvm -polly -mllvm -polly-codegen-scev
2013 Sep 13
2
[LLVMdev] [Polly] Compile-time and Execution-time analysis for the SCEV canonicalization
At 2013-09-09 13:07:07,"Tobias Grosser" <tobias at grosser.es> wrote:
>On 09/09/2013 05:18 AM, Star Tan wrote:
>>
>> At 2013-09-09 05:52:35,"Tobias Grosser" <tobias at grosser.es> wrote:
>>
>>> On 09/08/2013 08:03 PM, Star Tan wrote:
>>> Also, I wonder if your runs include the dependence analysis. If this is
>>> the