The inline and IPA pragmas tell KAP to inline/IPA the named functions.
#pragma _KAP [no]inline [here|routine|global] [(name[,name..])] #pragma _KAP [no]ipa [here|routine|global] [(name[,name..])]
The noinline and noipa pragmas tell KAP to not inline/analyze the named functions. These pragmas combine next-statement, entire routine (function), and global (entire program file) scope. If none of the optional elements are included, all functions referenced in the next statement that are in the inlining/analyzing universe are inlined/analyzed on that line.
These pragmas are disabled by default. You can enable them by
specifying any of the
/inlining (/ipa) command
qualifiers. Also, you can enable them without enabling any other
inlining/IPA with the
command qualifier. They are otherwise independent of the other
/inlining (/ipa) command qualifiers, and can be used
instead of, or in addition to, command-line controlled inlining and
The keywords including the word pragma must be lowercase. On some systems, the function names are case sensitive.
The effects of scope keywords on pragmas are as follows:
noinline/noipa, the pragma applies until the corresponding
noinline /noipa, the pragma applies until the corresponding
inline/ipapragma. Typically, global pragmas appear only at the top of the source file. The same function name may not appear in both global inlining and global IPA lists, either by pragmas or the
The optional names are function names. If any functions are named in the directive, it applies only to them. If NO function names are given, the pragma applies to ALL functions. The parentheses around the function names are not required if the list of function names is empty.
#pragma _KAP inline or
ipa names a function not in the inlining or IPA universe,
a Warning message is issued, and the pragma is ignored.