search for: inlinelimit

Is there a way to set how aggressive the inliner pass (createFunctionInliningPass) without going through the command line interface? Is there any reason InlineLimit isn't an argument to the createFunctionInliningPass function? Thanks, Robert

...y to set how aggressive the inliner pass > (createFunctionInliningPass) without going through the command line > interface? Nope. Well, you could call cl::ParseCommandLine yourself (passing in a static array) like llvm-gcc does, but other than that "no". > Is there any reason InlineLimit isn't an argument to the > createFunctionInliningPass function? Nope :). That would be a great enhancement. -Chris -- http://nondot.org/sabre/ http://llvm.org/

I am using llvm for source-to-source inlining. So I did: % llvm-gcc file_a.c file_b.c ... file_n.c -o file % opt -inline -inline-threshold=1000 < file.bc | llc -march=c > outfile.c Can anyone tell me how llvm determines if a function should be inlined, and what roll does "inline-threshold" play ? (Does the example mean that if the function body has fewer than 1000 instructions,

...; example mean that if the function body has fewer than 1000 > instructions, then it should be inlined ?) The LLVM inliner structure is implemented in llvm/lib/Transforms/IPO/Inliner.cpp which is a base implementation. There, you can see that -inline-threshold is a switch that provides value to InlineLimit which is used to initialize InlineThreshold member variable. This is compared with the output of getInlineCost() which is a virtual function. Currently, the inliner implemented in LLVM is InlineSimple.cpp in the same directory, which adds cost to functions if they have recursive calls, allocas, a...

...pass >> (createFunctionInliningPass) without going through the command line >> interface? > > Nope. Well, you could call cl::ParseCommandLine yourself (passing > in a > static array) like llvm-gcc does, but other than that "no". > >> Is there any reason InlineLimit isn't an argument to the >> createFunctionInliningPass function? > > Nope :). That would be a great enhancement. > > -Chris > > -- > http://nondot.org/sabre/ > http://llvm.org/ > _______________________________________________ > LLVM Developers mailing list...

...{"_ZL18nObjCPropertyImpls", "nObjCPropertyImpls"}, {"_ZL14nStaticAsserts", "nStaticAsserts"}, {"_ZL17nTranslationUnits", "nTranslationUnits"}, {"_ZL13StmtClassInfo", "StmtClassInfo"}, {"_ZL11InlineLimit", "InlineLimit"}, {"_ZL13HintThreshold", "HintThreshold"}, {"_ZL13Disable256Bit", "Disable256Bit"}, {"_ZL8NoFusing", "NoFusing"}, {"_ZL17PrintFailedFusing", "PrintFailedFusing"},...