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

Cryptol implementation of foreign functions #1397

Closed
qsctr opened this issue Aug 12, 2022 · 1 comment · Fixed by #1565
Closed

Cryptol implementation of foreign functions #1397

qsctr opened this issue Aug 12, 2022 · 1 comment · Fixed by #1565
Assignees
Labels
FFI Foreign function interface language Changes or extensions to the language

Comments

@qsctr
Copy link
Contributor

qsctr commented Aug 12, 2022

Allow foreign declarations to have an implementation in Cryptol as well. We could fall back to using the Cryptol implementation in situations where we can't do FFI, such as on unsupported platforms or in symbolic backends. It would also be nice to have some kind of integration with SAW so we can verify that the C function matches the Cryptol one.

@qsctr qsctr added language Changes or extensions to the language FFI Foreign function interface labels Aug 12, 2022
@weaversa
Copy link
Collaborator

I agree it would be incredibly helpful to allow foreign declarations to have an implementation in Cryptol, and any interpreter will use the shared library if it exists, and the Cryptol definition otherwise.

@qsctr qsctr self-assigned this Aug 9, 2023
@qsctr qsctr changed the title Cryptol implementation of foreign functions and SAW integration Cryptol implementation of foreign functions Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FFI Foreign function interface language Changes or extensions to the language
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants