Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically register FFI functions (dlsym path) #457

Open
PaulBone opened this issue Apr 1, 2023 · 0 comments
Open

Automatically register FFI functions (dlsym path) #457

PaulBone opened this issue Apr 1, 2023 · 0 comments
Labels
component: bytecode linker plzlnk, the bytecode linker component: compiler Concerning the compiler component: runtime Concerning the runtime system meta: triaged Has the issue been triaged yet? skill: C++ skill: mercury status: accepted A bug we intend to fix it. type: enhancement

Comments

@PaulBone
Copy link
Member

PaulBone commented Apr 1, 2023

Currently anyone using the FFI must arrange for foreign function implementations to be registered with the vm. This should be automatic and provided in two ways:

This bug will implement the second. This can be deferred to a later goal.

@PaulBone PaulBone added type: enhancement skill: C++ skill: mercury component: compiler Concerning the compiler component: runtime Concerning the runtime system meta: triaged Has the issue been triaged yet? status: accepted A bug we intend to fix it. component: bytecode linker plzlnk, the bytecode linker labels Apr 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: bytecode linker plzlnk, the bytecode linker component: compiler Concerning the compiler component: runtime Concerning the runtime system meta: triaged Has the issue been triaged yet? skill: C++ skill: mercury status: accepted A bug we intend to fix it. type: enhancement
Projects
None yet
Development

No branches or pull requests

1 participant