search for: pollys

I just checkout release_38 branches of llvm, clang and polly and built it on and x86 Ubuntu with cmake: CMAKE_BUILD_TYPE="Debug" CMAKE_INSTALL_PREFIX="$HOME/toolchain/install/llvm-3.8" LLVM_TARGETS_TO_BUILD="X86" cmake -G "Unix Makefiles" \ -DBUILD_SHARED_LIBS="ON" \ -DCMAKE_BUILD_TYPE=$CMAKE_BUILD_TYPE \

Hi, all I tried Polly installation on Ubuntu. On its building, it returned no errors. But when I run "make polly-test", it returns 11 unexpected failures as follows. ----------------------------------- ******************** Testing Time: 19.77s ******************** Failing Tests (11): Polly :: CodeGen/do_pluto_matmult.ll Polly :: CodeGen/loop_with_condition.ll Polly ::

Hi Tobias, At 2013-09-19 22:59:25,"Tobias Grosser" <tobias at grosser.es> wrote: >On 09/19/2013 04:46 PM, Star Tan wrote: >> Hi Tobias, >> >> >> I am trying to move Polly later. >> >> >> LLVM provides some predefined ExtensionPointTy: >> EP_EarlyAsPossible, >> EP_ModuleOptimizerEarly, >>

Dear Tobias Grosser, Thank you so much for your kind reply. Your advice is very helpful and inspiring. At 2013-03-18 20:40:50,"Tobias Grosser" <tobias at grosser.es> wrote: >On 03/17/2013 11:54 PM, Star Tan wrote: >> Hello Tobi, >> >> I am interested in Polly project. Polly seems to be a very promising tool to find out program parallelization based on LLVM

Hello Tobi, I am interested in Polly project. Polly seems to be a very promising tool to find out program parallelization based on LLVM infrastructure. However, I find that Polly analysis and optimization can consume significant compiling time, so I propose a GSoC project to reduce Polly compiling time and I hope my work can make the Polly tool more applicable for all LLVM users. I have done

H, Tobias Thank you for your reply. Tobias Grosser wrote: (Thu, 09 Jun 2011 15:41:05 -0300) >On 06/08/2011 01:17 AM, MORIYAMA Tomohiro wrote: >> Hi, all >> >> I tried Polly installation on Ubuntu. >> >> On its building, it returned no errors. >> But when I run "make polly-test", it returns 11 unexpected failures as >> follows. >>

Here is an update about moving Polly later. 1. Why does Polly generate incorrect code when we move Polly immediately after the loop rotating pass? It is mainly caused by a wrong polly merge block. When Polly detects a valid loop for Polyhedral transformations, it usually introduces a new basic block "polly.merge_new_and_old" after the original loop exit block. This new basic block

On 03/17/2013 11:54 PM, Star Tan wrote: > Hello Tobi, > > I am interested in Polly project. Polly seems to be a very promising tool to find out program parallelization based on LLVM infrastructure. However, I find that Polly analysis and optimization can consume significant compiling time, so I propose a GSoC project to reduce Polly compiling time and I hope my work can make the Polly

Dear Tobias Grosser, Today I have rebuilt the LLVM-Polly in Release mode. The configuration of my own testing machine is: Intel Pentium Dual CPU T2390(1.86GHz) with 2GB DDR2 memory. I evaluated the Polly using PolyBench and Mediabench. It takes too long time to evaluate the whole LLVM-testsuite, so I just choose the Mediabench from LLVM-testsuite. The preliminary results of Polly compiling

On 06/08/2011 01:17 AM, MORIYAMA Tomohiro wrote: > Hi, all > > I tried Polly installation on Ubuntu. > > On its building, it returned no errors. > But when I run "make polly-test", it returns 11 unexpected failures as > follows. > ----------------------------------- > ******************** > Testing Time: 19.77s > ******************** > Failing Tests

On 09/25/2013 04:55 AM, Star Tan wrote: > Here is an update about moving Polly later. Hi star tan, thanks for your report. > > 1. Why does Polly generate incorrect code when we move Polly immediately after the loop rotating pass? > > It is mainly caused by a wrong polly merge block. When Polly detects a valid loop for Polyhedral transformations, it usually introduces a new basic

Tobias, The most recent commits at svn revision 240868 have broken the Polly build on x86_64 on darwin... [ 57%] Building C object tools/polly/lib/CMakeFiles/Polly.dir/External/isl/isl_int_sioimath.c.o /sw/src/fink.build/llvm37-3.7.0-100/llvm-3.7.0.src/tools/polly/lib/External/isl/isl_int_sioimath.c:1:10: fatal error: 'malloc.h' file not found #include <malloc.h> ^ 1

On 05/03/2013 11:39 AM, Star Tan wrote: > 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.

(2011/06/10 13:25), Tobias Grosser wrote: > On 06/10/2011 12:00 AM, MORIYAMA Tomohiro wrote: >> H, Tobias >> Thank you for your reply. >> >> >> Tobias Grosser wrote: >>> Interesting. On what kind of Platform are you running this? Is it still >>> Ubuntu 11.04? I assume it's an intel platform, but is it a 32-bit or >>> 64bit? >>

(2011/06/10 14:01), Tobias Grosser wrote: > On 06/10/2011 01:52 AM, MORIYAMA Tomohiro wrote: >> (2011/06/10 13:25), Tobias Grosser wrote: >>> On 06/10/2011 12:00 AM, MORIYAMA Tomohiro wrote: >>>> H, Tobias >>>> Thank you for your reply. >>>> >>>> >>>> Tobias Grosser wrote: >>>>> Interesting. On what kind

Hi, polly is run very early and schedules the following passes before it runs: /// @brief Schedule a set of canonicalization passes to prepare for Polly /// /// The set of optimization passes was partially taken/copied from the /// set of default optimization passes in LLVM. It is used to bring the code /// into a canonical form that simplifies the analysis and optimization passes /// of Polly.

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

On 06/10/2011 12:00 AM, MORIYAMA Tomohiro wrote: > H, Tobias > Thank you for your reply. > > > Tobias Grosser wrote: >> Interesting. On what kind of Platform are you running this? Is it still >> Ubuntu 11.04? I assume it's an intel platform, but is it a 32-bit or 64bit? > > It is a little bit complicated. > > Intel Core i5 M520. > Ubuntu 11.04-i386

Hi Tobias, I am trying to move Polly later. LLVM provides some predefined ExtensionPointTy: EP_EarlyAsPossible, EP_ModuleOptimizerEarly, EP_LoopOptimizerEnd, EP_ScalarOptimizerLate, ... Currently Polly uses "EP_EarlyAsPossible" to run as early as possible. As what you suggested: >Instead of removing canonicalization passes, I believe we may want to >move

Hi Tobi, Rick is trying to set up a public buildbot for Polly on Windows. Right now the community version of polly does not build on Windows. We would like to make it possible to link polly statically to avoid several problems dealing with building polly as a DLL. I have a set of changes that make polly link statically in opt, clang, bugpoint, etc. These changes drop support for building