search for: deadtypeelim

...or quite a while and have just now bumped into this. Are there any options available for llvm-dis to emit complete types first? Perhaps there's another approach to get the optimizer and/or other tools to keep all the input types and retain their declaration order? I see there's an opton -deadtypeelim to the optimizer. I tried -nodeadtypeelim and -deadtypeelim=0 and -deadtypeelim=false, but it doesn't appear to accept any of those. Thanks for your help. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments...

...r-evolution -domfrontier -lcssa -indvars -domfrontier -scalar-evolution -lcssa -loop-unroll -instcombine -domtree -memdep -gvn -memcpyopt -sccp -instcombine -break-crit-edges -condprop -memdep -dse -mergereturn -postdomtree -postdomfrontier -adce -simplifycfg -strip-dead-prototypes -printusedtypes -deadtypeelim -constmerge -preverify -domtree -verify The script should look like: #!/bin/sh OPTS="-preverify -domtree -verify -lowersetjmp -raiseallocs -simplifycfg -domtree -domfrontier -mem2reg -globalopt -globaldce -ipconstprop -deadargelim -instcombine -simplifycfg -basiccg -prune-eh -inline...

...alar-evolution -loop-simplify -lcssa -iv-users -indvars -loop-idiom -loop-deletion -loop-unroll -instcombine -memdep -gvn -memdep -memcpyopt -sccp -instcombine -lazy-value-info -jump-threading -correlated-propagation -domtree -memdep -dse -adce -simplifycfg -strip-dead-prototypes -print-used-types -deadtypeelim -globaldce -constmerge -globalopt -ipsccp -deadargelim -instcombine -simplifycfg -basiccg -prune-eh -inline -functionattrs -scalarrepl-ssa -domtree -early-cse -simplify-libcalls -lazy-value-info -jump-threading -correlated-propagation -simplifycfg -instcombine -tailcallelim -simplifycfg -reassociat...

...tate -licm -lcssa -loop-unswitch -instcombine -scalar-evolution -lcssa -iv-users -indvars -loop-deletion -lcssa -loop-unroll -instcombine -memdep -gvn -memdep -memcpyopt -sccp -instcombine -break-crit-edges -condprop -domtree -memdep -dse -adce -simplifycfg -strip-dead-prototypes -print-used-types -deadtypeelim -constmerge llc: Pass Arguments: -preverify -domtree -verify -loops -loopsimplify -scalar-evolution -iv-users -loop-reduce -lowerinvoke -unreachableblockelim -codegenprepare -stack-protector -machine-function-analysis -machinedomtree -machine-loops -machinelicm -machine-sink -unreachable-mbb-elim...

...what happens to the optimization phases when the licm phase moves out loop invariant instructions to loop preheaders? opt -simplifycfg -instcombine -inline -globaldce -instcombine -simplifycfg -scalarrepl -mem2reg -verify -sccp -adce -licm -instcombine -dce -simplifycfg -deadargelim -globaldce -deadtypeelim < test.bc > test-opt.bc -- UGR -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100115/1b85fd7c/attachment.html>

...s projects such as PNaCl want to send LLVM bitcode over > the network, are there any proposed solutions for making LLVM bitcode > more compact? > > Removing or simplifying the names of local variables would be an > obvious thing to do. opt -globaldce -strip -strip-dead-prototypes -deadtypeelim -strip removes names of local vars (and more). > Is there anything else that could be done > without changing the bitcode format? (There's an obvious analogy with > JavaScript compression techniques.) Does anyone have any idea how > much it would help? You might try some other co...

...fycfg -prune-eh -inline -argpromotion -raise -tailduplicate > -simplifycfg -scalarrepl -instcombine -tailcallelim -simplifycfg > -loopsimplify -licm-reassociate -instcombine -indvars -loop-unroll > -instcombine-load-vn -gcse -sccp -instcombine -dse -mergereturn -adce > -simplifycfg -deadtypeelim -constmerge -verify -output=correct.txt > simple.out.bc > > bugpoint: Unknown command line argument '-instcombine-load-vn'. Try: > 'bugpoint --help' You need a space between -instcombine and -load-vn, they are separate passes. -- Misha Brukman :: http://misha.bruk...

Does anyone have experience to compile Linux kernel in LLVM-2.6? I am working on a C/C++ race detection framework and want to test in large applications. But I do have a lot of errors while compiling Linux kernel 2.6.3 using LLVM-2.6. Actually, I only need to get the .bc bitcode file. Anyboy does similar work before? Which Linux kernel version is used and any skills? Thanks. Lei /****** * Lei

...ion -raise -tailduplicate -simplifycfg -scalarrepl -instcombine -break-crit-edges -condprop -tailcallelim -simplifycfg -reassociate -loopsimplify -licm -instcombine -indvars -loop-unroll -instcombine -load-vn -gcse -sccp -instcombine -break-crit-edges -condprop -dse -mergereturn -adce -simplifycfg -deadtypeelim -constmerge -verify Target Data Layout Dummy PMF Interface Basic Alias Analysis (default AA impl) Basic Value Numbering (default GVN impl) Module Pass Manager PMF File Loader --PMF File Loader Raise allocations from calls to instructions --Raise allocations from calls to instructions Function...

According to the few tests I did, .ll.gz is more compact: 1.00 LLVM bitcode (.bc) 0.80 Gzipped LLVM bitcode (.bc.gz) 4.13 LLVM assembly (.ll) 0.68 Gzipped LLVM assembly (.ll.gz) However, there's not much in it, considering that a stripped native binary is about 0.40 on the same scale. So, seeing as projects such as PNaCl want to send LLVM bitcode over the network, are there any proposed

On Mon, 20 Mar 2006, Michael McCracken wrote: > Hi, I'm trying to access an analysis pass from the Inliner pass, and > I'm having a lot of trouble getting that to work - I can verify that > my pass is loaded and run (it is a dynamically loaded pass that is > part of an analysisgroup), however, when I access it using > getAnalysis<> from within Inliner::runOnSCC, I am

...> -simplifycfg -scalarrepl -instcombine -break-crit-edges -condprop > -tailcallelim -simplifycfg -reassociate -loopsimplify -licm > -instcombine -indvars -loop-unroll -instcombine -load-vn -gcse -sccp > -instcombine -break-crit-edges -condprop -dse -mergereturn -adce > -simplifycfg -deadtypeelim -constmerge -verify > Target Data Layout > Dummy PMF Interface > Basic Alias Analysis (default AA impl) > Basic Value Numbering (default GVN impl) > Module Pass Manager > PMF File Loader > --PMF File Loader > Raise allocations from calls to instructions > --Raise allo...

...tate -licm -lcssa -loop-unswitch -instcombine -scalar-evolution -lcssa -iv-users -indvars -loop-deletion -lcssa -loop-unroll -instcombine -memdep -gvn -memdep -memcpyopt -sccp -instcombine -break-crit-edges -condprop -domtree -memdep -dse -adce -simplifycfg -strip-dead-prototypes -print-used-types -deadtypeelim -constmerge This pass list is fine, it's equivalent to 'opt -std-compile-opts'. Nick > llc: > Pass Arguments: -preverify -domtree -verify -loops -loopsimplify -scalar-evolution -iv-users -loop-reduce -lowerinvoke -unreachableblockelim -codegenprepare -stack-protector -machine-...

Hi, I'm trying to access an analysis pass from the Inliner pass, and I'm having a lot of trouble getting that to work - I can verify that my pass is loaded and run (it is a dynamically loaded pass that is part of an analysisgroup), however, when I access it using getAnalysis<> from within Inliner::runOnSCC, I am instead getting the default, dummy version of my analysis, which should