procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Doc: always_inline attribute vs multiple TUs and LTO [PR113203]

Browse source 
gcc/ChangeLog
	PR ipa/113203
	* doc/extend.texi (Common Function Attributes): Explain how to
	use always_inline in programs that have multiple translation
	units, and that LTO inlining additionally needs optimization
	enabled.
This commit is contained in:
Sandra Loosemore 2025-04-15 03:49:06 +00:00
parent 764f02327f
commit fc89b1face
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
gcc/doc/extend.texi
View file

@ -1933,6 +1933,13 @@ Note that if such a function is called indirectly the compiler may
or may not inline it depending on optimization level and a failure
to inline an indirect call may or may not be diagnosed.
If you need to use the inlined function in multiple translation units,
you should put the @code{always_inline} attribute on a function
definition in a header file that is included in all translation units
where the function is used. Link-time optimization can inline
functions across translation units, but only if an optimization level
that normally enables inlining is additionally specified.
@cindex @code{artificial} function attribute
@item artificial
This attribute is useful for small inline wrappers that if possible