I Need A Reason!

[willow-ahrens]

This is a feature request for reasoning to be given when functions fail to inline. It would probably require a little bit of hacking to base, but something like the vectorization summaries that llvm provides about "This function didn't inline and why" would be really helpful. For example, "this function hit the recursion limiter," "this function has an unassigned type parameter", or "this function contains an error" would all be great things to know about why a function didn't inline, so that I can go and fix it.

[vchuravy]

The unassigned type-parameter we can check in Cthulhu, but Keno started to add a remarks framework to base in JuliaLang/julia#31000 which would have helped with the recursion heuristic limiter.

[vchuravy]

For checking unassigned type-parameters we can mirror CUDANative JuliaGPU/CUDAnative.jl#382

[DilumAluthge]

+1

I would love to see this feature added to Cthulhu. I often have a hard time figuring out why a function wasn't inlined.

Perhaps we could also print the cost (as per the inlining cost-model) next to each function?

[timholy]

Closed by #160

[vchuravy]

I think we still need an interface to export the inference remarks

Cthulhu.jl/src/interpreter.jl

Line 60 in e1e5ac6

function Compiler.add_remark!(interp::CthulhuInterpreter, sv::InferenceState, msg)