Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When you mark a function as inline, you hint the compiler that this function is a candidate for inlining. The compiler can still decide that it’s not a good idea, and ignore it.
Is there a way to see if the function gets inlined or not, without using the disassembler?
Is there some compiler warning that I don’t know about maybe?
What are the rules for inlining that the compiler uses? Are there constructs that cause a function to never get inlined for example?
The compiler emits a hint if it can’t inline your function. The documentation explains the rules for what can and cannot be inlined.
As for the discretionary decisions that the compiler takes as to whether or not to inline (as opposed to whether or not inlining is possible), they are not documented and can be considered an implementation detail.
I recall that you recently commented on one of my answers to a different question that a particular function was 10 times faster once inlined. Clearly you are interested in inlining but in that particular case I cannot believe such an enormous gain for a function with so many floating point operations. I suspect that inlining is not actually giving you the performance improvements that you think it does.