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

Properly defining two calling conventions for Core #487

Merged
merged 2 commits into from
Aug 13, 2024

Conversation

kmemarian
Copy link
Collaborator

This PR updates Core and its runtime to fully support two calling conventions differing on whether temporary objects for parameters are allocated by the caller (default) or the callee (the inner_arg_temps switch used by CN).

This should address issue #391.

* Normal_callconv: the original and default one, where the elaboration of C
  		   parameters are passed by pointers (to temporary objects
		   allocated and initialised by the caller).

* Inner_arg_callconv: used by CN, where the elaboration of C parameters are
  		      passed by value (except for the additional parameters of
		      variadic functions) and the temporary objects are allocated
		      by the callee in its body.

This commit updates the Core typing and runtime to support both
calling conventions.
@kmemarian kmemarian merged commit 431e3c1 into rems-project:master Aug 13, 2024
2 checks passed
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.

1 participant