search for: raiseallocs

Can I specify passes that I want run directly to llvm-gcc? I don't want all of -O3, for example. I tried llvm-gcc -raiseallocs ..., but that didn't work. I also tried running cc1 directly and it didn't take -raiseallocs as a parameter either. Duncan Sands wrote: > On Tuesday 28 April 2009 04:02:47 am Ryan M. Lefever wrote: >> I assume that when -O3 (or O2 or O1) is passed to llvm-gcc, then it >>...

After LLVM rev 84987, the RaiseAllocations pass no longer exists. llvm-gcc needs to be patched: Index: gcc/llvm-linker-hack.cpp =================================================================== --- gcc/llvm-linker-hack.cpp (revision 84984) +++ gcc/llvm-linker-hack.cpp (working copy) @@ -80,7 +80,6 @@ llvm::createJumpThreadingPass(); llvm::createFunctionInliningPass();

Thanks for the help. When I run the following (where $llvm is the path to my llvm installation): $llvm/bin/llvm-gcc -c -o - -O1 tmp.c -emit-llvm -mllvm --disable-llvm-optzns | $llvm/bin/opt -raiseallocs I get the following error: cc1: error: unrecognized command line option "-fdisable-llvm-optzns" I am running llvm 2.5. I performed a $llvm/libexec/gcc/i686-pc-linux-gnu/4.2.1/cc1 --help and didn't see -fdisable-llvm-optzns or anything similar. Do you know what might be going o...

On Tuesday 28 April 2009 09:19:19 am Ryan M. Lefever wrote: > Can I specify passes that I want run directly to llvm-gcc? I don't want > all of -O3, for example. I tried llvm-gcc -raiseallocs ..., but that > didn't work. I also tried running cc1 directly and it didn't take > -raiseallocs as a parameter either. You are better off run passes explicitly using opt. Try this: llvm-gcc -c -o - -O1 my_proc.c -emit-llvm -mllvm --disable-llvm-optzns | opt list_of_passes Pass...

...e time for why poolalloc wouldn't transform calls to malloc() in my program, until I noticed that it handles calls to malloc() (eg, stdlib pass) -- but only transforms MallocInst's. Is there a general policy on how passes should behave? Should they handle both representations, is doing -raiseallocs the preferred way, or do we explicitely not want any single policy (ie, are there any hidden problems)? Perhaps this could also get a FAQ entry or sth. like that. Torvald

I assume that when -O3 (or O2 or O1) is passed to llvm-gcc, then it utilizes opt. How do I determine what passes opt runs? How do I determine what external tools (and arguments) llvm-gcc is invoking? Regards, Ryan

On Tuesday 28 April 2009 04:02:47 am Ryan M. Lefever wrote: > I assume that when -O3 (or O2 or O1) is passed to llvm-gcc, then it > utilizes opt. How do I determine what passes opt runs? How do I > determine what external tools (and arguments) llvm-gcc is invoking? It doesn't invoke opt, it runs the passes directly. You can see what passes it is running by passing

Hi, I'm currently implementing some optimization passes for LLVM and I came across a problem. I'm new to LLVM so if this question has been asked before please kindly tell me where can I find the answer. There are 2 types of AllocationInst - Alloca and Malloc. But most of the time from the compiled byte code I can only find the Alloca statement (actually I never come across a

Hello, have a short look at the following simple c-prog: #include <stdlib.h> int main(int argc, char* argv[]) { void* buf = malloc(10 * sizeof(char*)); /* do sth with buf, so that it is not "optimized away" */ return 0; } When you compile this using a plain llvm-gcc, the call to libc-malloc is left inside.But compiling it with -O2 alters the call to llvm::MallocInst. Now

...sertion failures for the pass dependencies. This is when it in PointerCompress::getAnalysisUsage tries to register the the BU pass as required. I.e. when AU.addRequired<CompleteBUDataStructures>(); is called. $ opt -f -load ~/Projects/llvmstuff/opt/poolalloc/lib/ libpoolalloc.dylib -raiseallocs -poolalloc-passing-all-pools - pointercompress llist-noopt.bc -o llist-dp.bc Assertion failed: ((P->getPotentialPassManagerType() < RequiredPass- >getPotentialPassManagerType()) && "Unable to handle Pass that requires lower level Analysis pass"), function addLower...

...ng the way proposed by Chris, it is good to have a script to scan the standard LLVM transform pass list. We can get the standard compile optimization pass list by: $ opt -std-compile-opts -debug-pass=Arguments foo.bc > /dev/null Pass Arguments: -preverify -domtree -verify -lowersetjmp -raiseallocs -simplifycfg -domtree -domfrontier -mem2reg -globalopt -globaldce -ipconstprop -deadargelim -instcombine -simplifycfg -basiccg -prune-eh -inline -argpromotion -tailduplicate -simplify-libcalls -instcombine -jump-threading -simplifycfg -domtree -domfrontier -scalarrepl -instcombine -break-crit-edges...

...t; transform calls > to malloc() in my program, until I noticed that it handles calls to > malloc() > (eg, stdlib pass) -- but only transforms MallocInst's. > > Is there a general policy on how passes should behave? Should they > handle both > representations, is doing -raiseallocs the preferred way, or do we > explicitely not want any single policy (ie, are there any hidden > problems)? > Perhaps this could also get a FAQ entry or sth. like that. > > Torvald > _______________________________________________ > LLVM Developers mailing list > LLVMdev a...

instcombine doesn't seem to be doing it. From my testing it seems to only occur when I use -indvars after a long string of commands. For example: llvm-as < test_fc_27.ll | opt -preverify -domtree -verify -lowersetjmp -raiseallocs -simplifycfg -domtree -domfrontier -mem2reg -globalopt -globaldce -ipconstprop -deadargelim -instcombine -simplifycfg -ba siccg -prune-eh -inline -argpromotion -simplify-libcalls -instcombine -jump-threading -simplifycfg -domtree -domfrontier -scalarrepl -instcombine -break-crit-...

On Thu, Dec 4, 2008 at 7:08 PM, Chris Lattner <clattner at apple.com> wrote: > > On Dec 4, 2008, at 8:58 AM, Villmow, Micah wrote: > > What optimization pass promotes 32 bit math operations to 64 bit operations > so I can disable it? I have code that works fine with optimizations turned > off but fails with it turned on because of this stage. > > > Do you have a

...dependencies. > > This is when it in PointerCompress::getAnalysisUsage tries to register > the the BU pass as required. I.e. when > AU.addRequired<CompleteBUDataStructures>(); is called. > > > $ opt -f -load ~/Projects/llvmstuff/opt/poolalloc/lib/ > libpoolalloc.dylib -raiseallocs -poolalloc-passing-all-pools - > pointercompress llist-noopt.bc -o llist-dp.bc > > Assertion failed: ((P->getPotentialPassManagerType() < RequiredPass- > >getPotentialPassManagerType()) && "Unable to handle Pass that > requires lower level Analysis pass"),...

...malloc() in my program, until I noticed that it handles calls to > > malloc() > > (eg, stdlib pass) -- but only transforms MallocInst's. > > > > Is there a general policy on how passes should behave? Should they > > handle both > > representations, is doing -raiseallocs the preferred way, or do we > > explicitely not want any single policy (ie, are there any hidden > > problems)? > > Perhaps this could also get a FAQ entry or sth. like that. > > > > Torvald > > _______________________________________________ > > LLVM Devel...

...For example, NaN's, infinities, and other special values are represented in their IEEE hexadecimal format so that assembly and disassembly do not cause any bits to change in the constants." When I compile the following simple program with llvm-gcc -O0 -c --emit-llvm, run it through opt --raiseallocs --lowerconstexps and llvm-dis, I get a floating point number in hexadecimal that is not one of the above mentioned special forms. #include <stdlib.h> #include <stdio.h> int main() { float f = 5.66; return (int)(f + 1.33); } It will emit: ... store float 0x4016A3D700000000, f...

...dependencies. > > This is when it in PointerCompress::getAnalysisUsage tries to register > the the BU pass as required. I.e. when > AU.addRequired<CompleteBUDataStructures>(); is called. > > > $ opt -f -load ~/Projects/llvmstuff/opt/poolalloc/lib/ > libpoolalloc.dylib -raiseallocs -poolalloc-passing-all-pools - > pointercompress llist-noopt.bc -o llist-dp.bc > > Assertion failed: ((P->getPotentialPassManagerType() < RequiredPass- > >getPotentialPassManagerType()) && "Unable to handle Pass that > requires lower level Analysis pass"),...

...This is when it in PointerCompress::getAnalysisUsage tries to register >> the the BU pass as required. I.e. when >> AU.addRequired<CompleteBUDataStructures>(); is called. >> >> >> $ opt -f -load ~/Projects/llvmstuff/opt/poolalloc/lib/ >> libpoolalloc.dylib -raiseallocs -poolalloc-passing-all-pools - >> pointercompress llist-noopt.bc -o llist-dp.bc >> >> Assertion failed: ((P->getPotentialPassManagerType() < RequiredPass- >> >getPotentialPassManagerType()) && "Unable to handle Pass that >> requires lower level A...

...function inlining is only performed by clang (i.e. only on a module-by-module basis), and not by llvm-link or llc. This can be seen in the resulting pass options with -O3 (obtained using '-Xclang -debug-only=Execution' and '-Xlinker -debug-only=Execution'): Clang: Pass Arguments: -raiseallocs -simplifycfg -domtree -domfrontier -mem2reg -globalopt -globaldce -ipconstprop -deadargelim -instcombine -simplifycfg -basiccg -prune-eh -functionattrs -inline -argpromotion -simplify-libcalls -instcombine -jump-threading -simplifycfg -domtree -domfrontier -scalarrepl -instcombine -break-crit-edges...