optimizer: supports callsite annotations of inlining, fixes #18773 #41328

@inline

Enable `@inline`/`@noinline` annotations on function callsites. From #40754. Now `@inline` and `@noinline` can be applied to a code block and then the compiler will try to (not) inline calls within the block: ```julia @inline f(...) # The compiler will try to inline `f` @inline f(...) + g(...) # The compiler will try to inline `f`, `g` and `+` @inline f(args...) = ... # Of course annotations on a definition is still allowed ``` Here are couple of notes on how those callsite annotations will work: - callsite annotation always has the precedence over the annotation applied to the definition of the called function, whichever we use `@inline`/`@noinline`: ```julia @inline function explicit_inline(args...) # body end let @noinline explicit_inline(args...) # this call will not be inlined end ``` - when callsite annotations are nested, the innermost annotations has the precedence ```julia @noinline let a0, b0 = ... a = @inline f(a0) # the compiler will try to inline this call b = notinlined(b0) # the compiler will NOT try to inline this call return a, b end ``` They're both tested and included in documentations.

Co-authored-by: Jameson Nash <[email protected]>

- remove preprocessed flags from `jl_code_info_set_ir` - fix duplicated definition warning - add and fix comments

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

optimizer: supports callsite annotations of inlining, fixes #18773 #41328

optimizer: supports callsite annotations of inlining, fixes #18773 #41328

Commits on Aug 31, 2021