Does GCC, when compiling C++ code, ever try to optimize for speed by choosing to inline functions that are not marked with the inline
keyword?
views:
645answers:
5Yes, especially if you have a high level of optimizations enabled.
There is a flag you can provide to the compiler to disable this: -fno-inline-functions.
Yes. Any compiler is free to inline any function whenever it thinks it is a good idea. GCC does that as well.
At -O2 optimization level the inlining is done when the compiler thinks it is worth doing (a heuristic is used) and if it will not increase the size of the code. At -O3 it is done whenever the compiler thinks it is worth doing, regardless of whether it will increase the size of the code. Additionally, at all levels of optimization (enabled optimization that is), static functions that are called only once are inlined.
If you use '-finline-functions' or '-O3' it will inline functions. You can also use '-finline_limit=N' to tune how much inlining it does.
"-O3 This option turns on more expensive optimizations, such as function inlining"
Yes, it does, although it will also generate a non-inlined function body for non-static
non-inline
functions as this is needed for calls from other translation units.
For inline
functions, it is an error to fail to provide a function body if the function is used in any particular translation unit so this isn't a problem.