Skip to content

Conversation

vtjnash
Copy link
Member

@vtjnash vtjnash commented Jun 6, 2025

In preparation for giving us the option of not storing code that does not seem useful immediately, but which we previously kept around just in case inference or codegen (always_inline) ever needed to decide if it was worthwhile to inline later. And also for investigating issues like the recently closed #58449 to examine whether the code was removed for either heuristic or correctness reasons.

In preparation for giving us the option of not storing code that does
not seem useful immediately, but which we previously kept around just in
case inference or codegen (always_inline) ever needed to decide if it
was worthwhile to inline later. And also for investigating issues like
the recently closed #58449 to examine whether the code was removed for
either heuristic or correctness reasons.
@vtjnash vtjnash requested a review from JeffBezanson June 6, 2025 19:21
Co-authored-by: Justin Willmert <[email protected]>
@vtjnash vtjnash merged commit 6121477 into master Jun 12, 2025
5 of 7 checks passed
@vtjnash vtjnash deleted the jn/inferred_inline_cost branch June 12, 2025 16:18
nilesh646 pushed a commit to nilesh646/julia that referenced this pull request Jun 17, 2025
…ce (JuliaLang#58662)

In preparation for giving us the option of not storing code that does
not seem useful immediately, but which we previously kept around just in
case inference or codegen (always_inline) ever needed to decide if it
was worthwhile to inline later. And also for investigating issues like
the recently closed JuliaLang#58449 to examine whether the code was removed for
either heuristic or correctness reasons.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Performance regression in ccall on master and 1.12-beta
3 participants