search for: tailcallelim

Hi from what I have figured out, the pass "TailCallElim" is being done in what I would call the "opt" phase of optimization. The "StackColoring" is being done in the "llc" phase. opt -> llc, so TailCallElim is always ahead. Now I would like to add something (my reusealloca idea) in "StackColoring" to...

...********************************************************************* 1. Compile the source code to unoptimized IRs: clang -c -emit-llvm -O0 test.c -o test.bc 2. Run opt with a set of IR->IR passes, e.g., opt -simplifycfg -sroa -inferattrs -globalopt -instcombine -simplifycfg -prune-eh -inline -tailcallelim -simplifycfg -loop-simplify -lcssa -loop-rotate -licm -gvn -verify test.bc -o test.bc 3. Run llc with -O0: llc -file-type=obj test.bc -o test.o 4. Last link all the object files: clang -O0 test1.o test2.o -o test ********************************************************************************* Tha...

...ttps://github.com/llvm/llvm-project/blob/cbe77ca9bd05393b1df1abf016b01f44d1d10a49/llvm/lib/Transforms/Scalar/TailRecursionElimination.cpp#L275 Looking through the tests that cover this scenario (https://github.com/llvm/llvm-project/blob/e29874eaa04d24b8c67776bf5729474d671a58f6/llvm/test/Transforms/TailCallElim/basic.ll#L66), I found it referring to rdar://14324281 and PR962. What are they? These haven't been updated since 2014, so I wonder what is the latest state and have them been resolved? cc nicholas who authored the original code. Thanks! -- Xun

...last test result sended. New regressions: Regression.Assembler.ConstantExprFold : FAIL , expected PASS Regression.CodeGen.Generic.2004-04-09-SameValueCoalescing: FAIL , expected PASS Regression.Transforms.PRE.basictest : FAIL , expected PASS Regression.Transforms.TailCallElim.tail_call_with_branch: FAIL , expected PASS Full log attached. --- STATISTICS --------------------------------------------------------------- 920 tests total 856 ( 93%) tests as expected 6 ( 1%) tests unexpected FAIL 58 ( 6%) tests unexpected PASS --- TESTS W...

...ized 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 -l...

...hould be possible according to the Source Level Debugging with LLVM: "you get accurate stack traces despite tail call elimination and inlining),". However, in my examples, %llvm.dbg.stoppoint and %llvm.dbg.region.end get inserted between the tail call and the return statement, which stop tailcallelim unless I remove them manually. Thank you for your help, Anna.

...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 >...

...sicaa -preverify -domtree -verify -lowersetjmp -globalopt -ipsccp -deadargelim -instcombine -simplifycfg -basiccg -prune-eh -inline -functionattrs -argpromotion -scalarrepl-ssa -domtree -early-cse -simplify-libcalls -lazy-value-info -jump-threading -correlated-propagation -simplifycfg -instcombine -tailcallelim -simplifycfg -reassociate -domtree -loops -loop-simplify -lcssa -loop-rotate -licm -lcssa -loop-unswitch -instcombine -scalar-evolution -loop-simplify -lcssa -iv-users -indvars -loop-idiom -loop-deletion -loop-unroll -instcombine -memdep -gvn -memdep -memcpyopt -sccp -instcombine -lazy-value-info -...

...argetlibinfo -targetdata -no-aa -tbaa -basicaa -globalopt -ipsccp -deadargelim -instcombine -simplifycfg -basiccg -prune-eh -inline -functionattrs -argpromotion -scalarrepl-ssa -domtree -early-cse -simplify-libcalls -lazy-value-info -jump-threading -correlated-propagation -simplifycfg -instcombine -tailcallelim -simplifycfg -reassociate -domtree -loops -loop-simplify -lcssa -loop-rotate -licm -lcssa -loop-unswitch -instcombine -scalar-evolution -loop-simplify -lcssa -indvars -loop-idiom -loop-deletion -loop-unroll -memdep -gvn -memdep -memcpyopt -sccp -instcombine -lazy-value-info -jump-threading -correla...

...cker -basicaa -verify-di -ipsccp > -globalopt -deadargelim -domtree -instcombine -simplifycfg -basiccg > -prune-eh -inline-cost -inline -functionattrs -argpromotion -sroa -domtree > -early-cse -lazy-value-info -jump-threading -correlated-propagation > -simplifycfg -domtree -instcombine -tailcallelim -simplifycfg -reassociate > -domtree -loops -loop-simplify -lcssa -loop-rotate -licm -loop-unswitch > -instcombine -scalar-evolution -loop-simplify -lcssa -indvars -loop-idiom > -loop-deletion -function_tti -loop-unroll -memdep -mldst-motion -domtree > -memdep -gvn -memdep -memcpyopt -s...

...mtree -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-edges -condprop -tailcallelim -simplifycfg -reassociate -domtree -loops -loopsimplify -domfrontier -scalar-evolution -lcssa -loop-rotate -licm -lcssa -scalar-evolution -lcssa -loop-index-split -instcombine -scalar-evolution -lcssa -simplifycfg -view-cfg Doesn't cause it, but llvm-as < test_fc_27.ll | opt...

...lias -assumption-tracker -basicaa -verify-di -ipsccp -globalopt -deadargelim -domtree -instcombine -simplifycfg -basiccg -prune-eh -inline-cost -inline -functionattrs -argpromotion -sroa -domtree -early-cse -lazy-value-info -jump-threading -correlated-propagation -simplifycfg -domtree -instcombine -tailcallelim -simplifycfg -reassociate -domtree -loops -loop-simplify -lcssa -loop-rotate -licm -loop-unswitch -instcombine -scalar-evolution -loop-simplify -lcssa -indvars -loop-idiom -loop-deletion -function_tti -loop-unroll -memdep -mldst-motion -domtree -memdep -gvn -memdep -memcpyopt -sccp -domtree -instco...

...run some canonicalization passes before you actually run the scalar evolution pass. Most of the time these passes should be sufficient: -correlated-propagation -mem2reg -instcombine -loop-simplify -indvars But in Polly we use e.g.: -basicaa -mem2reg -simplify-libcalls -simplifycfg -instcombine -tailcallelim -loop-simplify -lcssa -loop-rotate -lcssa -loop-unswitch -instcombine -loop-simplify -lcssa -indvars -loop-deletion -instcombine -polly-prepare -polly-region-simplify -indvars If you send me the .ll file you run your tool on, I could take a closer look. Cheers and all the best Tobi

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

...an load Polly into clang and use the following command (-O3 is important): > clang test.c -O3 -Xclang -load -Xclang lib/LLVMPolly.so -mllvm -debug-pass=Arguments Pass Arguments: -targetdata -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...

...***************** > ********************* > 1. Compile the source code to unoptimized IRs: > clang -c -emit-llvm -O0 test.c -o test.bc > 2. Run opt with a set of IR->IR passes, e.g., > opt -simplifycfg -sroa -inferattrs -globalopt -instcombine -simplifycfg > -prune-eh -inline -tailcallelim -simplifycfg -loop-simplify -lcssa > -loop-rotate -licm -gvn -verify test.bc -o test.bc > 3. Run llc with -O0: > llc -file-type=obj test.bc -o test.o > 4. Last link all the object files: > clang -O0 test1.o test2.o -o test > ********************************************************...

...alar/TailRecursionElimination.cpp > test/Bindings/llvm-c/Inputs/invalid.ll.bc > test/Bindings/llvm-c/invalid-bitcode.test > test/Bitcode/attributes.ll > test/Bitcode/invalid.ll > test/Bitcode/invalid.ll.bc > test/CodeGen/X86/attr-notail.ll > test/Transforms/TailCallElim/notail.ll > > > > _______________________________________________ > llvm-commits mailing list > llvm-commits at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits -------------- next part -------------- An HTML attachment was scrubbed... URL: <http...

Thanks Vladimir. That's great! Glad you got it working. BTW, the failures you're seeing have been experienced by Chris and I as well. Chris is diligently working on making the LLVM processing more consistent so he track down the problem. A week ago or so, these tests passed at 100%. Reid. On Sun, 2004-06-20 at 15:50, Vladimir Merzliakov wrote: > In attached file. > > Vladimir

In attached file. Vladimir -------------- next part -------------- A non-text attachment was scrubbed... Name: test2004_06_20.log Type: application/octet-stream Size: 88488 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20040620/98042f01/attachment.obj>

...com/llvm/llvm-project/blob/cbe77ca9bd05393b1df1abf016b01f44d1d10a49/llvm/lib/Transforms/Scalar/TailRecursionElimination.cpp#L275 > > Looking through the tests that cover this scenario > (https://github.com/llvm/llvm-project/blob/e29874eaa04d24b8c67776bf5729474d671a58f6/llvm/test/Transforms/TailCallElim/basic.ll#L66), > I found it referring to rdar://14324281 and PR962. What are they? > These haven't been updated since 2014, so I wonder what is the latest > state and have them been resolved? > > cc nicholas who authored the original code. > > Thanks! >