[TASK] Handle calling through function pointers #100
Labels
enhancement
New feature or request
Milestone
Comments
iamrecursion
added a commit
that referenced
this issue
Jan 15, 2025
Function pointers are now handled according to the memory model documentation, ensuring that we can generate code that will allow us to call through opaque function pointers correctly. Note that this commit only encompasses the compiler-side part of this work, with more work to be done in the linker to handle generation of the meta-dispatch functions for each function type. Closes #100
iamrecursion
added a commit
that referenced
this issue
Jan 15, 2025
Function pointers are now handled according to the memory model documentation, ensuring that we can generate code that will allow us to call through opaque function pointers correctly. Note that this commit only encompasses the compiler-side part of this work, with more work to be done in the linker to handle generation of the meta-dispatch functions for each function type. Closes #100
2 tasks
2 tasks
iamrecursion
added a commit
that referenced
this issue
Jan 15, 2025
Function pointers are now handled according to the memory model documentation, ensuring that we can generate code that will allow us to call through opaque function pointers correctly. Note that this commit only encompasses the compiler-side part of this work, with more work to be done in the linker to handle generation of the meta-dispatch functions for each function type. Closes #100
iamrecursion
added a commit
that referenced
this issue
Jan 15, 2025
Function pointers are now handled according to the memory model documentation, ensuring that we can generate code that will allow us to call through opaque function pointers correctly. Note that this commit only encompasses the compiler-side part of this work, with more work to be done in the linker to handle generation of the meta-dispatch functions for each function type. Closes #100
iamrecursion
added a commit
that referenced
this issue
Jan 15, 2025
Function pointers are now handled according to the memory model documentation, ensuring that we can generate code that will allow us to call through opaque function pointers correctly. Note that this commit only encompasses the compiler-side part of this work, with more work to be done in the linker to handle generation of the meta-dispatch functions for each function type. Closes #100
iamrecursion
added a commit
that referenced
this issue
Jan 15, 2025
Function pointers are now handled according to the memory model documentation, ensuring that we can generate code that will allow us to call through opaque function pointers correctly. Note that this commit only encompasses the compiler-side part of this work, with more work to be done in the linker to handle generation of the meta-dispatch functions for each function type. Closes #100
iamrecursion
added a commit
that referenced
this issue
Jan 15, 2025
Function pointers are now handled according to the memory model documentation, ensuring that we can generate code that will allow us to call through opaque function pointers correctly. Note that this commit only encompasses the compiler-side part of this work, with more work to be done in the linker to handle generation of the meta-dispatch functions for each function type. It also makes some minor changes to the mangler to allow it to handle reserved names in a more sensible way. Closes #100
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently both the
callandinvokeopcodes do not handle the ability to call via a function pointer argument. This is due to the fact that we think it is unlikely to be needed, at least initially. Nevertheless, this is something we want to support, and so both opcodes need to be enhanced to deal with it.The primary difficulty relates to the memory model, and what it actually means to have a function pointer on our architecture. We need to work out how we get them, and how we then jump to them from the context of FLO.
Spec
callandinvoketo handle these cases.The text was updated successfully, but these errors were encountered: