search for: compare_to

...uated our r187102 patch file that avoids expensive failure string operations in normal execution. Specifically, I evaluated two cases for it: Polly-NoCodeGen: clang -O3 -load LLVMPolly.so -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none http://188.40.87.11:8000/db_default/v4/nts/16?compare_to=9&baseline=9&aggregation_fn=median Polly-Opt: clang -O3 -load LLVMPolly.so -mllvm -polly http://188.40.87.11:8000/db_default/v4/nts/18?compare_to=11&baseline=11&aggregation_fn=median The "Polly-NoCodeGen" case is mainly used to compare the compile-time performance for th...

...07/30/2013 10:03 AM, Star Tan wrote: > Hi Tobias and all Polly developers, > > I have re-evaluated the Polly compile-time performance using newest > LLVM/Polly source code. You can view the results on > http://188.40.87.11:8000 > <http://188.40.87.11:8000/db_default/v4/nts/16?compare_to=9&baseline=9&aggregation_fn=median>. > > Especially, I also evaluated ourr187102 patch file that avoids expensive > failure string operations in normal execution. Specifically, I evaluated > two cases for it: > > Polly-NoCodeGen: clang -O3 -load LLVMPolly.so -mllvm >...

...ar Tan wrote: >> Hi Tobias and all Polly developers, >> >> I have re-evaluated the Polly compile-time performance using newest >> LLVM/Polly source code. You can view the results on >> http://188.40.87.11:8000 >> <http://188.40.87.11:8000/db_default/v4/nts/16?compare_to=9&baseline=9&aggregation_fn=median>. >> >> Especially, I also evaluated ourr187102 patch file that avoids expensive >> failure string operations in normal execution. Specifically, I evaluated >> two cases for it: >> >> Polly-NoCodeGen: clang -O3 -load...

...om/tanstar/581bcea1e4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 >>>> >>>> >>>> Based on the comparison between "clang -O3" and "polly -O3" listed on: >>>>       http://188.40.87.11:8000/db_default/v4/nts/18?compare_to=14&baseline=14 >>> >>> Please compare against clang -O3 -load LLVMPolly.so, otherwise >>> especially the compile time of the small binaries includes the overhead >>> of loading the Polly shared object file. >> >> In fact, the compile-time overhead...

...t; Hi Tobias and all Polly developers, >>> >>> I have re-evaluated the Polly compile-time performance using newest >>> LLVM/Polly source code. You can view the results on >>> http://188.40.87.11:8000 >>> <http://188.40.87.11:8000/db_default/v4/nts/16?compare_to=9&baseline=9&aggregation_fn=median>. >>> >>> Especially, I also evaluated ourr187102 patch file that avoids expensive >>> failure string operations in normal execution. Specifically, I evaluated >>> two cases for it: >>> >>> Polly-NoC...

...Polly developers, >>>> >>>> I have re-evaluated the Polly compile-time performance using newest >>>> LLVM/Polly source code. You can view the results on >>>> http://188.40.87.11:8000 >>>> <http://188.40.87.11:8000/db_default/v4/nts/16?compare_to=9&baseline=9&aggregation_fn=median>. >>>> >>>> Especially, I also evaluated ourr187102 patch file that avoids expensive >>>> failure string operations in normal execution. Specifically, I evaluated >>>> two cases for it: >>>> &g...

...(run 33): -O3 -Xclang -load -Xclang LLVMPolly.so -mllvm -polly -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none *pBasic without any canonicalization (run 34): -O3 -Xclang -load -Xclang LLVMPolly.so Impact of SCEV canonicalization: http://188.40.87.11:8000/db_default/v4/nts/32?compare_to=34&baseline=34 Impact of default canonicalization: http://188.40.87.11:8000/db_default/v4/nts/33?compare_to=34&baseline=34 Comparison of SCEV canonicalization with default canonicalization: http://188.40.87.11:8000/db_default/v4/nts/32?compare_to=33&baseline=33 As we expecte...

...4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 >>>>> >>>>> >>>>> Based on the comparison between "clang -O3" and "polly -O3" listed on: >>>>> http://188.40.87.11:8000/db_default/v4/nts/18?compare_to=14&baseline=14 >>>> >>>> Please compare against clang -O3 -load LLVMPolly.so, otherwise >>>> especially the compile time of the small binaries includes the overhead >>>> of loading the Polly shared object file. >>> >>> In...

...ad -Xclang LLVMPolly.so -mllvm -polly -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none > *pBasic without any canonicalization (run 34): -O3 -Xclang -load -Xclang LLVMPolly.so > > > Impact of SCEV canonicalization: > http://188.40.87.11:8000/db_default/v4/nts/32?compare_to=34&baseline=34 > Impact of default canonicalization: > http://188.40.87.11:8000/db_default/v4/nts/33?compare_to=34&baseline=34 > Comparison of SCEV canonicalization with default canonicalization: > http://188.40.87.11:8000/db_default/v4/nts/32?compare_to=33&baselin...

...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 files for ScopDetect/ScopInfo/ScopDependences/..., we have significantly reduced the compile-time overhead of Polly for a large number of benchmarks,...

...://gist.github.com/tanstar/581bcea1e4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 >>> >>> >>> Based on the comparison between "clang -O3" and "polly -O3" listed on: >>> http://188.40.87.11:8000/db_default/v4/nts/18?compare_to=14&baseline=14 >> >> Please compare against clang -O3 -load LLVMPolly.so, otherwise >> especially the compile time of the small binaries includes the overhead >> of loading the Polly shared object file. > > In fact, the compile-time overhead of loading Polly shared...

...t;>      https://gist.github.com/tanstar/581bcea1e4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 >> >> >> Based on the comparison between "clang -O3" and "polly -O3" listed on: >>      http://188.40.87.11:8000/db_default/v4/nts/18?compare_to=14&baseline=14 > >Please compare against clang -O3 -load LLVMPolly.so, otherwise  >especially the compile time of the small binaries includes the overhead  >of loading the Polly shared object file. In fact, the compile-time overhead of loading Polly shared object file is very small...

...-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 16 benchmarks regressed. Especially, with those recent performance-oriented patch files for ScopDetect/ScopInfo/ScopDependences/..., we have significantly reduced the co...

...llvm -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 is available now. >> Overall, there are 198 benchmarks improved and 16 benchmarks regressed. Especially, with those recent performance-oriented patch files for ScopDetect/ScopIn...

....so -mllvm -polly -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none >> *pBasic without any canonicalization (run 34): -O3 -Xclang -load -Xclang LLVMPolly.so >> >> >> Impact of SCEV canonicalization: >> http://188.40.87.11:8000/db_default/v4/nts/32?compare_to=34&baseline=34 >> Impact of default canonicalization: >> http://188.40.87.11:8000/db_default/v4/nts/33?compare_to=34&baseline=34 >> Comparison of SCEV canonicalization with default canonicalization: >> http://188.40.87.11:8000/db_default/v4/nts/32?compare_t...

...fect 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_default/v4/nts/18?compare_to=24&baseline=24 The only difference between the two runs is whether they use the r187102 patch file, i.e., run_id=18 is with the r187102 patch file, while run_id=24 is without the r187102 patch file. Results show that this patch file significantly reduces compile time for tramp3d-v4(24.41%),...

...import_and_report email_config, toAddress, success, commit) File "/home/simon/work/lnt.svn/lnt/util/NTEmailReport.py", line 16, in emailReport was_added, will_commit) File "/home/simon/work/lnt.svn/lnt/util/NTEmailReport.py", line 53, in getReport result=result, compare_to=compare_to) File "/home/simon/work/lnt.svn/lnt/server/reporting/runs.py", line 195, in generate_run_report start_time=start_time) File "/home/simon/work/python.sandbox/lib/python2.6/site-packages/Flask-0.9-py2.6.egg/flask/templating.py", line 123, in render_template...

...can be viewed on: > https://gist.github.com/tanstar/581bcea1e4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 > > > Based on the comparison between "clang -O3" and "polly -O3" listed on: > http://188.40.87.11:8000/db_default/v4/nts/18?compare_to=14&baseline=14 Please compare against clang -O3 -load LLVMPolly.so, otherwise especially the compile time of the small binaries includes the overhead of loading the Polly shared object file. > we can see Polly's compile-time overhead is mainly resulted by some expensive Polly passes...

...LVM test-ssuite. Results can be viewed on: https://gist.github.com/tanstar/581bcea1e4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 Based on the comparison between "clang -O3" and "polly -O3" listed on: http://188.40.87.11:8000/db_default/v4/nts/18?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 percen...

...un vs run comparison and fill in the runids of the 2 runs you want to compare. For example, the following URL is a comparison of green-dragon-07-x86_64-O3-flto vs green-dragon-06-x86_64-O0-g on the public llvm.org/perf<http://llvm.org/perf> server: http://llvm.org/perf/db_default/v4/nts/70644?compare_to=70634 I had to manually look up and fill in the run ids 70644 and 70634. It would be great if there was a better way to be able to do these kind of comparisons - i.e. not having to manually fill in run ids, but having a webui to easily find and pick the runs you want to compare. (As an aside: I fin...