Displaying 6 results from an estimated 6 matches for "r187116".
Did you mean:
218116
2013 Aug 01
4
[LLVMdev] [Polly] Update of Polly compile-time performance on LLVM test-suite
...the ignore_small abs value to 0.05 from the original 0.01, which means benchmarks with the performance delta less then 0.05s would be skipped. In that case, the results seem to be much more stable.
However, I have noticed that there are many other Polly patches between the two version r185399 and r187116. They may also affect the compile-time performance. I would re-evaluate LLVM-testsuite to see the performance improvements caused only by our
>
>Also, it may be interesting to compare against the non-polly case to see
>how much overhead there is still due to our scop detetion.
>
>&...
2013 Aug 01
0
[LLVMdev] [Polly] Update of Polly compile-time performance on LLVM test-suite
>However, I have noticed that there are many other Polly patches between the two version r185399 and r187116. They may also affect the compile-time performance. I would re-evaluate LLVM-testsuite to see the performance improvements caused only by our patch file.
Performance evaluation for our single "ScopDetection String Operation Patch" (r187102) can be viewed on:
http://188.40.87.11:8000/db_...
2013 Jul 30
3
[LLVMdev] [Polly] Update of Polly compile-time performance on LLVM test-suite
...21?compare_to=16&baseline=16&aggregation_fn=median
pOpt-ScopBottomUp: clang -O3 -load LLVMPolly.so (v.s. LLVMPolly-ScopBottomUp.so) -mllvm -polly
http://188.40.87.11:8000/db_default/v4/nts/19?compare_to=18&baseline=18&aggregation_fn=median
(*Both of these results are based on LLVM r187116, which has included the r187102 patch file that we discussed above)
Please notice that this patch file will lead to some errors in Polly-tests, so the data shown here can not be regards as confident results. For example, this patch can significantly reduce the compile-time overhead of SingleSourc...
2013 Jul 31
0
[LLVMdev] [Polly] Update of Polly compile-time performance on LLVM test-suite
...p;baseline=16&aggregation_fn=median
> pOpt-ScopBottomUp: clang -O3 -load LLVMPolly.so (v.s.
> LLVMPolly-ScopBottomUp.so) -mllvm -polly
> http://188.40.87.11:8000/db_default/v4/nts/19?compare_to=18&baseline=18&aggregation_fn=median
> (*Both of these results are based on LLVM r187116, which has included
> the r187102 patch file that we discussed above)
>
> Please notice that this patch file will lead to some errors in
> Polly-tests, so the data shown here can not be regards as confident
> results. For example, this patch can significantly reduce the
> compile-...
2013 Aug 01
0
[LLVMdev] [Polly] Update of Polly compile-time performance on LLVM test-suite
...e ignore_small abs value to 0.05 from the original 0.01, which means benchmarks with the performance delta less then 0.05s would be skipped. In that case,the results seem to be much more stable.
> However, I have noticed that there are many other Polly patches between the two version r185399 and r187116. They may also affect the compile-time performance. I would re-evaluate LLVM-testsuite to see the performance improvements caused only by our
I doubt the Polly changes changed performance a much. However, there
have been huge numbers of patches to LLVM/clang. Those obviously changed
performance....
2013 Aug 02
1
[LLVMdev] [Polly] Update of Polly compile-time performance on LLVM test-suite
...nore_small abs value to 0.05 from the original 0.01, which means benchmarks with the performance delta less then 0.05s would be skipped. In that case,the results seem to be much more stable.
>> However, I have noticed that there are many other Polly patches between the two version r185399 and r187116. They may also affect the compile-time performance. I would re-evaluate LLVM-testsuite to see the performance improvements caused only by our
>
>I doubt the Polly changes changed performance a much. However, there
>have been huge numbers of patches to LLVM/clang. Those obviously changed...