Skip to content

Conversation

@topolarity
Copy link
Member

@topolarity topolarity commented Feb 18, 2023

In the event that multiple libjulia-internals have been loaded, we need to make sure that the right copy is placed first in the DynamicLibrary search order so that calls to runtime intrinsics from the JIT are resolved to it.

This is relevant, e.g., when we try to ccall into a PackageCompiler.jl-created shared library.

@topolarity topolarity added backport 1.8 Change should be backported to release-1.8 backport 1.9 Change should be backported to release-1.9 labels Feb 21, 2023
We need to make sure that libjulia-internal is loaded and placed first in the
DynamicLibrary search order so that calls to runtime intrinsics are resolved
to the correct library when multiple libjulia-*'s have been loaded (e.g. when
we `ccall` into a PackageCompiler.jl-created shared library).
@topolarity topolarity force-pushed the orcjit-dylib-search-order branch from 150cf60 to 604ab69 Compare February 24, 2023 20:14
@KristofferC KristofferC merged commit fd45943 into JuliaLang:master Feb 28, 2023
@topolarity topolarity deleted the orcjit-dylib-search-order branch February 28, 2023 18:14
KristofferC pushed a commit that referenced this pull request Mar 3, 2023
We need to make sure that libjulia-internal is loaded and placed first in the
DynamicLibrary search order so that calls to runtime intrinsics are resolved
to the correct library when multiple libjulia-*'s have been loaded (e.g. when
we `ccall` into a PackageCompiler.jl-created shared library).

(cherry picked from commit fd45943)
@KristofferC KristofferC mentioned this pull request Mar 3, 2023
50 tasks
KristofferC pushed a commit that referenced this pull request Mar 3, 2023
We need to make sure that libjulia-internal is loaded and placed first in the
DynamicLibrary search order so that calls to runtime intrinsics are resolved
to the correct library when multiple libjulia-*'s have been loaded (e.g. when
we `ccall` into a PackageCompiler.jl-created shared library).

(cherry picked from commit fd45943)
@KristofferC KristofferC removed the backport 1.9 Change should be backported to release-1.9 label Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 1.8 Change should be backported to release-1.8

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants