[LLVMdev] How to make Polly ignore some non-affine memory accesses

Marcello Maggioni hayarms at gmail.com
Mon Oct 24 15:32:36 PDT 2011

Strange , with --enable-shared (I use auto tool by the way ...) it gives:

MacBook-Pro-di-Marcello:examples Kariddi$ ./compile_ex.sh not_so_simple_loop
clang (LLVM option parsing): Unknown command line argument
'-enable-polly-viewer'.  Try: 'clang (LLVM option parsing) -help'
clang (LLVM option parsing): Did you mean '-enable-polly-vector'?

Seems like it doesn't compile the viewer option ...

2011/10/24 Marcello Maggioni <hayarms at gmail.com>:
> It works!! :)
> I'll try also enable-shared , to see if it's possible to use it
> without the patch and report
> 2011/10/24 Tobias Grosser <tobias at grosser.es>:
>> On 10/23/2011 02:31 PM, Tobias Grosser wrote:
>>> On 10/22/2011 08:41 AM, Marcello Maggioni wrote:
>> [..]
>>>> Seems like it tries to load a symbol that it doesn't find ...
>>>> I have synchronized all clang/llvm/polly to the latest version and I
>>>> compiled them all together. Loading polly with "opt" works strangely
>>>> ... :
>>>> opt -S -load ${PATH_TO_POLLY_LIB}/LLVMPolly.dylib -mem2reg -no-aa
>>>> -targetlibinfo -tbaa -basicaa -preverify -domtree -verify -mem2reg
>>>> -instcombine -simplifycfg -tailcallelim -simplifycfg -reassociate
>>>> -domtree -loops -loop-simplify -lcssa -loop-rotate -instcombine
>>>> -scalar-evolution -loop-simplify -lcssa -indvars -polly-prepare
>>>> -postdomtree -domfrontier -regions -polly-region-simplify
>>>> -scalar-evolution -loop-simplify -lcssa -indvars -postdomtree
>>>> -domfrontier -regions  -loop-simplify -indvars  -enable-iv-rewrite
>>>> not_so_simple_loop.s
>>>> strange ...
>>> Very strange. I have seen such problems previously and they were often
>>> related to enabling rtti (runtime type info) or exceptions in Polly, but
>>> no clang or the other way around. I am not sure if this is the case her.
>>> Another possibility is that clang does not use the RegionInfo stuff and
>>> it gets dead code eliminated.
>> I am even more convinced this is the case. Can you try the attached patch
>> and report if it works for you?
>> Cheers
>> Tobi

More information about the llvm-dev mailing list