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

Need wasm64 syscalls #816

Closed
trcrsired opened this issue Jan 15, 2024 · 1 comment
Closed

Need wasm64 syscalls #816

trcrsired opened this issue Jan 15, 2024 · 1 comment

Comments

@trcrsired
Copy link

trcrsired commented Jan 15, 2024

As I mentioned before, this can be done by creating separate APIs for wasm32 and wasm64.

API is 32bit
API_wasm64 is 64 bit.

The codegen from preview2 breaks my wasi-libc builds.

The size header file can switch to size_t with WASI_IMPORT macro defined.

@alexcrichton
Copy link
Member

Thanks for the report! 64-bit memories, however, are not currently specified with the component model, so it's best to discuss on that upstream issue first. Once that's settled then code generators such as this can start growing support for 64-bit bindings.

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

No branches or pull requests

2 participants