I have studied that
The inline specifier is a hint to the compiler that it should attempt to generate code [...] inline rather than laying down the code for the function once and then calling through the usual function call mechanism.
Questions:
- If optimization is turned off for the GCC compiler, is the inline specifier ignored?
- When inline functions are called recursively, which compiler option determines the 'depth of inlining', until it follows the normal function call mechanism ?
- If the inline function is invoked inside a for loop, does the same 'depth of inlining' come into the picture ?