[llvm-commits] [llvm-gcc-4.2] r51608 - /llvm-gcc-4.2/trunk/gcc/llvm-backend.cpp

Duncan Sands baldrick at free.fr
Wed May 28 12:04:27 PDT 2008


Hi Dale,

> And honoring no-inline and always-inline is needed for correctness
> (assuming we accept GCC extensions as part of the language).

for these it is irrelevant whether we run the LLVM inliner or not.
* always-inline is handled by the gcc inliner using the usual gcc logic.
* noinline: if the LLVM inliner is not run then these functions are not
inlined; if it is run then they are not inlined either because they are
noted in the llvm.noinline metadata.

Ciao,

Duncan.



More information about the llvm-commits mailing list