Skip to content

Conversation

topolarity
Copy link
Member

This is another step in the long-term direction to have type-inference fully-explore the code graph we want to emit, largely side-stepping the vestigial jl_type_infer paths that we still have in type-inference for ccallable (and OpaqueClosure)

This is needed for juliac, since the trim checks in codegen check if code was enqueued in the workqueue as expected.

This is another step in the long-term direction to have type-inference
fully-explore the code graph we want to emit, largely side-stepping the
vestigial `jl_type_infer` paths that we still have in type-inference
for ccallable (and OpaqueClosure)

This is needed for `juliac`, since the trim checks in codegen check if
code was enqueued in the workqueue as expected.
@topolarity topolarity added the trimming Issues with trimming functionality or PR's relevant to its performance/functionality label Jan 24, 2025
Co-authored-by: Jameson Nash <vtjnash@gmail.com>
@topolarity topolarity merged commit d5523b6 into JuliaLang:master Jan 28, 2025
7 checks passed
@topolarity topolarity deleted the ct/enqueue-ccallable-ci branch February 1, 2025 00:38
serenity4 pushed a commit to serenity4/julia that referenced this pull request May 1, 2025
This is another step in the long-term direction to have type-inference
fully-explore the code graph we want to emit, largely side-stepping the
vestigial `jl_type_infer` paths that we still have in type-inference for
ccallable (and OpaqueClosure)

This is needed for `juliac`, since the trim checks in codegen check if
code was enqueued in the workqueue as expected.

---------

Co-authored-by: Jameson Nash <vtjnash@gmail.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
trimming Issues with trimming functionality or PR's relevant to its performance/functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants