Ruby  3.4.0dev (2024-11-05 revision 348a53415339076afc4a02fcd09f3ae36e9c4c61)
Macros
forceinline.h File Reference

(348a53415339076afc4a02fcd09f3ae36e9c4c61)

Defines RBIMPL_ATTR_FORCEINLINE. More...

#include "ruby/internal/compiler_since.h"
#include "ruby/internal/has/attribute.h"
Include dependency graph for forceinline.h:
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Macros

#define RBIMPL_ATTR_FORCEINLINE()   __attribute__((__always_inline__)) inline
 Wraps (or simulates) __forceinline. More...
 

Detailed Description

Defines RBIMPL_ATTR_FORCEINLINE.

Author
Ruby developers ruby-.nosp@m.core.nosp@m.@ruby.nosp@m.-lan.nosp@m.g.org
Warning
Symbols prefixed with either RBIMPL or rbimpl are implementation details. Don't take them as canon. They could rapidly appear then vanish. The name (path) of this header file is also an implementation detail. Do not expect it to persist at the place it is now. Developers are free to move it anywhere anytime at will.
Note
To ruby-core: remember that this header can be possibly recursively included from extension libraries written in C++. Do not expect for instance __VA_ARGS__ is always available. We assume C99 for ruby itself but we don't assume languages of extension libraries. They could be written in C++98.

Definition in file forceinline.h.

Macro Definition Documentation

◆ RBIMPL_ATTR_FORCEINLINE

#define RBIMPL_ATTR_FORCEINLINE ( )    __attribute__((__always_inline__)) inline

Wraps (or simulates) __forceinline.

MSVC complains on declarations like static inline __forceinline void foo(). It seems MSVC's inline and __forceinline are mutually exclusive. We have to mimic that behaviour for non-MSVC compilers.

Definition at line 35 of file forceinline.h.