views:

2078

answers:

8
+17  A: 

There is no generic C++ way to FORCE the compiler to create inline functions. Note the word 'hint' in the text you quoted - the compiler is not obliged to listen to you.

If you really, absolutely have to make something be in-line, you'll need a compiler specific keyword, OR you'll need to use macros instead of functions.

EDIT: njsf gives the proper gcc keyword in his response.

Michael Kohne
+1  A: 

Whether to inline is up to the compiler. Is it free to ignore the inline hint. Some compilers have a specific keyword (like __forceinline in VC++) but even with such a keyword virtual calls to virtual member functions will not be inlined.

sharptooth
+7  A: 

Do you compile with optimizations turned on ?

+2  A: 

It is a hint and the complier can choice to ignore the hint. I think I read some where that GCC generally ignore it. I remeber hearing there was a flag but it still does not work in 100% of cases. (I have not found a link yet).

Flag: -finline-functions is turned on at -O3 optimisation level.

David Allan Finch
I believe the main difference gcc pays to "inline" is that it means the function can be up to 600 instructions big and still get inlined, while functions not declared inline considered for auto inlining with -finline-functions have to be less than 300 instructions. You can mess with all these numbers and more using --param to adjust things with names like max-inline-insns-auto (but you need a pretty good reason to; the defaults are sound). Changing the difference between the numbers for explicit and auto inlining means you can effectively make inline have more or less of an effect though.
timday
That is very interesting. Thanks.
David Allan Finch
+20  A: 

Like Michael Kohne mentioned, the inline keyword is always a hint, and GCC in the case of your function decided not to inline it.

Since you are using Gcc you can force inline with the __attribute((always_inline)).

Example:

 /* Prototype.  */
 inline void foo (const char) __attribute__((always_inline));

Source:GCC inline docs

njsf
upvoted for the gcc-fu
Paul Morie
Yeah, but if the questioner goes away and starts pasting __attribute__((always_inline)); onto all his functions instead of just compiling with -O3, we've failed.
timday
Agreed. I guess I am still an optimist and believe most people have some common sense ;-)
njsf
+6  A: 

Are you looking at a debug build (optimizations disabled)? Compilers usually disable inlining in "debug" builds because they make debugging harder.

In any case, the inline specified is indeed a hint. The compiler is not required to inline the function. There are a number of reasons why any compiler might decide to ignore an inline hint:

  • A compiler might be simple, and not support inlining
  • A compiler might use an internal algorithm to decide on what to inline and ignore the hints.
    (sometimes, the compiler can do a better job than you can possibly do at choosing what to inline, especially in complex architectures like IA64)
  • A compiler might use its own heuristics to decide that despite the hint, inlining will not improve performance
Euro Micelli
+2  A: 

Inline is nothing more than a suggestion to the compiler that, if it's possible to inline this function then the compiler should consider doing so. Some functions it will inline automatically because they are so simple, and other functions that you suggest it inlines it won't because they are to complex.

Also, I noticed that you are doing a debug build. I don't actually know, but it's possible that the compiler disables inlining for debug builds because it makes things difficult for the debugger...

Graham
A: 

I faced similar problems and found that it only works if the inline function is written in a header file.

sybreon