search for: pollycc

...M test-suite with latest LLVM (r188054) and Polly (r187981).  Results can be viewed on: http://188.40.87.11:8000. There are mainly five new tests 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&b...

...). Results can be viewed on: http://188.40.87.11:8000. Hi Star Tan, thanks for the update. > There are mainly five new tests 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_defaul...

...E}.ll -S -emit-llvm -mllvm -polly -O0 to also enable -enable-iv-rewrite you need: clang -Xclang -load -Xclang ${POLLY_DLIB} ${FILE}.c -o ${FILE}.ll -S -emit-llvm -mllvm -polly -O0 -mllvm -enable-iv-rewrite. I just tried to detect the scops myself. I used for this the following command: alias pollycc='~/Projekte/polly/build_clang/bin/clang -Xclang -load \ -Xclang ~/Projekte/polly/build_clang/lib/LLVMPolly.so' pollycc -mllvm -polly-show test.c -c -mllvm -enable-iv-rewrite -mllvm -polly -O3 It detects all three loops. Can you reproduce this? Cheers Tobi --------------...

...ave a need for it before >>>switching to it. >>> >> I have evaluated Polly compile-time performance for the following options: >> >> clang: clang -O3 (runid: 14) >> >> pBasic: clang -O3 -load LLVMPolly.so (runid:15) >> >> pNoGen: pollycc -O3 -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none (runid:16) >> >> pNoOpt: pollycc -O3 -mllvm -polly-optimizer=none (runid:17) >> >> pOpt: pollycc -O3 (runid:18) >> >> For example, you can view the comparison between "clang" and &...

...etection actually helps here. >As this is a larger patch, we should really have a need for it before >switching to it. > I have evaluated Polly compile-time performance for the following options: clang: clang -O3 (runid: 14) pBasic: clang -O3 -load LLVMPolly.so (runid:15) pNoGen: pollycc -O3 -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none (runid:16) pNoOpt: pollycc -O3 -mllvm -polly-optimizer=none (runid:17) pOpt: pollycc -O3 (runid:18) For example, you can view the comparison between "clang" and "pNoGen" with: http://188.40.87.11:8000/db_de...

Hello Tobi, Thank you for the quick reply. I updated my complete build suite with your script (http://polly.grosser.es/polly.sh). The make-test fails with some errors, the rest went smoothly; -- Exit Code: 1 Command Output (stderr): -- LLVM ERROR: Could not resolve external global address: stdout -- ******************** Testing Time: 10.01s ******************** Failing Tests (3): Polly ::

...s a larger patch, we should really have a need for it before >>switching to it. >> > I have evaluated Polly compile-time performance for the following options: > > clang: clang -O3 (runid: 14) > > pBasic: clang -O3 -load LLVMPolly.so (runid:15) > > pNoGen: pollycc -O3 -mllvm -polly-optimizer=none -mllvm -polly-code-generator=none (runid:16) > > pNoOpt: pollycc -O3 -mllvm -polly-optimizer=none (runid:17) > > pOpt: pollycc -O3 (runid:18) > > For example, you can view the comparison between "clang" and "pNoGen" with:...

...rt mode. All Polly, LLVM and > Cloog source code are checked out from SVN at April 24, 2013. Can you give the svn revision / git hash for the checkouts of LLVM, Polly, isl, cloog and polybench. > Table 1 and table 2 show the compile-time overhead of Polly. Five cases are tested: > (alias pollycc="clang -O3 -load LLVMPolly.so -mllvm -polly) > * **clang**: clang -O3 > * **pBasic**: clang -O3 -load LLVMPolly.so > * **pNoGen**: pollycc -O3 -mllvm -polly-optimizer=none -mllvm -polly-code-generatorr=none > * **pNoOpt**: pollycc -O3 -mllvm -polly-optimizer=none > * **pOpt**:...

...> > to also enable -enable-iv-rewrite you need: > > clang -Xclang -load -Xclang ${POLLY_DLIB} ${FILE}.c -o ${FILE}.ll -S -emit-llvm -mllvm -polly -O0 -mllvm -enable-iv-rewrite. > > I just tried to detect the scops myself. I used for this the following command: > > alias pollycc='~/Projekte/polly/build_clang/bin/clang -Xclang -load \ > -Xclang ~/Projekte/polly/build_clang/lib/LLVMPolly.so' > > pollycc -mllvm -polly-show test.c -c -mllvm -enable-iv-rewrite -mllvm -polly -O3 > > It detects all three loops. Can you reproduce this? >...

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

...> Our evaluation is based on Intel Pentium Dual CPU T2390(1.86GHz) with > 2GB DDR2 memory. Each benchmark is run multiple times and data are > collected using ministat (https://github.com/codahale/ministat). Results > are shown in table 1 and table 2. Five cases are tested: (alias > pollycc="clang -O3 -load LLVMPolly.so -mllvm -polly) *clang: clang -O3 > *pLoad: clang -O3 -load LLVMPolly.so *pNoGen:pollycc -O3 -mllvm > -polly-optimizer=none -mllvm -polly-code-generatorr=none *pNoOpt:pollycc > -O3 -mllvm -polly-optimizer=none *polly: pollycc -O3 > > Table 1: Compile...

...me consuming. Their git hash value are: Cloog: 77c44782f4cbf6d60a7dbfe996b0649336ec7205 Polly: 5f3abecad642a6646c53cbd39879091da87c3c37 LLVM: d050e96133fac8565e3bb1eabe9a587dd5a6ac4d > >> Table 1 and table 2 show the compile-time overhead of Polly. Five cases are tested: >> (alias pollycc="clang -O3 -load LLVMPolly.so -mllvm -polly) >> * **clang**: clang -O3 >> * **pBasic**: clang -O3 -load LLVMPolly.so >> * **pNoGen**: pollycc -O3 -mllvm -polly-optimizer=none -mllvm -polly-code-generatorr=none >> * **pNoOpt**: pollycc -O3 -mllvm -polly-optimizer=none &...

.../188.40.87.11:8000. > >Hi Star Tan, > >thanks for the update. > >> There are mainly five new tests 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...

On 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

Hi all, I have updated my GSoS proposal: "FastPolly: Reducing LLVM-Polly Compiling overhead" (https://gist.github.com/tanstar/5441808). I think the pass ordering problem you discussed early can be also investigated in this project! Is there any comment or advice about my proposal? I appreciate all your help and advice. Thanks, Star Tan Proposal:

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. Especially, I also evaluated 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

How to feed pocc by jscop files which are made with -polly-export-jscop? 2011/4/8 ether zhhb <etherzhhb at gmail.com>: > Hi, > > 2011/4/8 Vlad Krylov <krvladislav at gmail.com>: >> Hi. >> >> I see that to detect scops firstly we search for regions in CFG ( by >> RegionInfo ) and then select regions that answer some requirements ( >> in

Hello, Le 12/12/2016 à 18:29, Hans Wennborg a écrit : > +Sylvestre who knows about these things. > > On Thu, Dec 8, 2016 at 2:24 AM, Kris van Rens via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> L.S., >> >> I'm currently in the process of creating Debian packages for >> clang/llvm release 3.9.0. For this I'm using the steps as explained on