search for: dpolybench_use_scalar_lb

...s or hints on this problem? OK. I think in this case the problem is actually to figure out why Polly does not give a speedup in terms of execution time, because we have seen large speedups for 2mm and 3mm. Here is what I see: 2mm$ polly-clang 2mm.c -O3 -I ../../../utilities/ -DPOLYBENCH_TIME -DPOLYBENCH_USE_SCALAR_LB -mllvm -polly-ignore-aliasing 2mm$ time ./a.out 18.217128 real 0m18.256s user 0m18.128s sys 0m0.064s 2mm$ polly-clang 2mm.c -O3 -I ../../../utilities/ -DPOLYBENCH_TIME -DPOLYBENCH_USE_SCALAR_LB -mllvm -polly-ignore-aliasing -mllvm -polly 2mm$ time ./a.out 4.986877 real 0m5.036s user 0m4.940s sys...

...;OK. I think in this case the problem is actually to figure out why Polly >does not give a speedup in terms of execution time, because we have seen >large speedups for 2mm and 3mm. > >Here is what I see: > >2mm$ polly-clang 2mm.c -O3 -I ../../../utilities/ -DPOLYBENCH_TIME >-DPOLYBENCH_USE_SCALAR_LB -mllvm -polly-ignore-aliasing >2mm$ time ./a.out >18.217128 > >real 0m18.256s >user 0m18.128s >sys 0m0.064s >2mm$ polly-clang 2mm.c -O3 -I ../../../utilities/ -DPOLYBENCH_TIME >-DPOLYBENCH_USE_SCALAR_LB -mllvm -polly-ignore-aliasing -mllvm -polly >2mm$ time ./a.out >4...

Hi all, It seems that Polly's code generation can leads to high compile-time overhead, especially for PolyBench applications such as 2mm, 3mm, gemm, syrk, etc. Some basic evaluation and analysis for Polly's code generation can be referred to http://llvm.org/bugs/show_bug.cgi?id=16898. Currently, we can choose to run -polly-code-generator=cloog or -polly-code-generator=isl for code

...problem is actually to figure out why Polly >> does not give a speedup in terms of execution time, because we have seen >> large speedups for 2mm and 3mm. >> >> Here is what I see: >> >> 2mm$ polly-clang 2mm.c -O3 -I ../../../utilities/ -DPOLYBENCH_TIME >> -DPOLYBENCH_USE_SCALAR_LB -mllvm -polly-ignore-aliasing >> 2mm$ time ./a.out >> 18.217128 >> >> real 0m18.256s >> user 0m18.128s >> sys 0m0.064s >> 2mm$ polly-clang 2mm.c -O3 -I ../../../utilities/ -DPOLYBENCH_TIME >> -DPOLYBENCH_USE_SCALAR_LB -mllvm -polly-ignore-aliasing -ml...

...e out why Polly >>> does not give a speedup in terms of execution time, because we have seen >>> large speedups for 2mm and 3mm. >>> >>> Here is what I see: >>> >>> 2mm$ polly-clang 2mm.c -O3 -I ../../../utilities/ -DPOLYBENCH_TIME >>> -DPOLYBENCH_USE_SCALAR_LB -mllvm -polly-ignore-aliasing >>> 2mm$ time ./a.out >>> 18.217128 >>> >>> real 0m18.256s >>> user 0m18.128s >>> sys 0m0.064s >>> 2mm$ polly-clang 2mm.c -O3 -I ../../../utilities/ -DPOLYBENCH_TIME >>> -DPOLYBENCH_USE_SCALAR_LB -...

...ly-optimizer=none -mllvm -polly-code-generatorr=none > * **pNoOpt**: pollycc -O3 -mllvm -polly-optimizer=none > * **pOpt**: pollycc -O3 You probably want to add a couple of additional parameters here to ensure we detect all scops in polybench. I would add -mllvm -polly-ignore-aliasing and -DPOLYBENCH_USE_SCALAR_LB You can use '-mllvm -debug-only=polly-cloog' to see if the kernels are properly detected. I get the following output: alias polly-clang alias polly-clang='~/Projekte/polly/build/bin/clang -Xclang -load -Xclang ~/Projekte/polly/build/lib/LLVMPolly.so' grosser at tobilaptop:~/Proje...

Dear Tobias, Thank you very much for your very helpful advice. Yes, -debug-pass and -time-passes are two very useful and powerful options when evaluating the compile-time of each compiler pass. They are exactly what I need! With these options, I can step into details of the compile-time overhead of each pass. I have finished some preliminary testing based on two randomly selected files from

On 04/30/2013 04:13 PM, Star Tan wrote: > Hi all, [...] > How could I find out where the time is spent on between two adjacent Polly passes? Can anyone give me some advice? Hi Star Tan, I propose to do the performance analysis using the 'opt' tool and optimizing LLVM-IR, instead of running it from within clang. For the 'opt' tool there are two commands that should help

...-polly-code-generatorr=none >> * **pNoOpt**: pollycc -O3 -mllvm -polly-optimizer=none >> * **pOpt**: pollycc -O3 > >You probably want to add a couple of additional parameters here to >ensure we detect all scops in polybench. I would add -mllvm >-polly-ignore-aliasing and -DPOLYBENCH_USE_SCALAR_LB > >You can use '-mllvm -debug-only=polly-cloog' to see if the kernels >are properly detected. I get the following output: > >alias polly-clang >alias polly-clang='~/Projekte/polly/build/bin/clang -Xclang -load >-Xclang ~/Projekte/polly/build/lib/LLVMPolly.so' &...