search for: output_inline

I am investigating some inlining issue, so I did llvm-gcc aaa.c bbb.c ... nnn.c -o output opt -inline -inline-threshold=xxx < output.bc | llc -march=c > output_inline.c 1) I noticed that even if I set xxx to 0 or even a very small negative number, many functions are eliminated. I am wondering if these functions are inlined by the frontend, or identified as deadcode. For instance, SPEC2k bzip2 has 79 functions, after these two steps, only 61 functions are le...

Long Fei wrote: > > I am investigating some inlining issue, so I did > > llvm-gcc aaa.c bbb.c ... nnn.c -o output > opt -inline -inline-threshold=xxx < output.bc | llc -march=c > > output_inline.c I am unsure of whether the LLVM GCC frontend does any inlining. However, I do know that your methods above run the LLVM inlining pass, albeit indirectly. If you use llvm-gcc to generate and link LLVM bytecode files (as you do in the example above), llvm-gcc runs gccas and gccld (the optimizi...

...ld or just read their source code. John Criswell wrote: > Long Fei wrote: > >> >> I am investigating some inlining issue, so I did >> >> llvm-gcc aaa.c bbb.c ... nnn.c -o output >> opt -inline -inline-threshold=xxx < output.bc | llc -march=c > >> output_inline.c > > > I am unsure of whether the LLVM GCC frontend does any inlining. > However, I do know that your methods above run the LLVM inlining pass, > albeit indirectly. > > If you use llvm-gcc to generate and link LLVM bytecode files (as you > do in the example above), llvm-...

...ohn Criswell wrote: > >> Long Fei wrote: >> >>> >>> I am investigating some inlining issue, so I did >>> >>> llvm-gcc aaa.c bbb.c ... nnn.c -o output >>> opt -inline -inline-threshold=xxx < output.bc | llc -march=c > >>> output_inline.c >> >> >> I am unsure of whether the LLVM GCC frontend does any inlining. However, I >> do know that your methods above run the LLVM inlining pass, albeit >> indirectly. >> >> If you use llvm-gcc to generate and link LLVM bytecode files (as you do in...

On Thu, 7 Jul 2005, Henrik Bach wrote: > The 'pthread_once' is located in the native library binary file: > /usr/lib/libpthread.a. I've also included the path to the library in > LLVM_LIB_SEARCH_PATH environment variable. If libpthread.a is a static library, lli won't be successful loading it. Try relinking lli, but add this to its tools/lli/Makefile: TOOLLINKOPTS :=

Hi LLVM'ers, I'm trying to build the DotGNU project with the LLVM-tools. After minor modifications of source and build code and some configure housekeeping, it seems that I've managed so far to build all the DotGNU tools. However, when extensively using the DotGNU tools I get this error message: make[1]: Entering directory `/home/hb/projects/build/LLVM/pnet-1-1/samples'