Skip to content

Document Argument passing for _BitInt types #239

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

Closed
pinskia opened this issue Dec 2, 2024 · 1 comment · Fixed by #240
Closed

Document Argument passing for _BitInt types #239

pinskia opened this issue Dec 2, 2024 · 1 comment · Fixed by #240

Comments

@pinskia
Copy link

pinskia commented Dec 2, 2024

Forwarded from https://hachyderm.io/@[email protected]/113574803870036780 .

The current BasicCABI.md does not document how _BitInt types are passed and it would be good to document it as such.

Note if someone does a GCC backend for WebAssembly, GCC folks in general has decided the ABI for _BitInt needs to be documented before it having it implemented too.

See ARM-software/abi-aa#175, riscv-non-isa/riscv-elf-psabi-doc#300 and https://gitlab.com/x86-psABIs/x86-64-ABI/-/merge_requests/32 for examples on how other ABIs (have or will have document it).

sunfishcode added a commit to sunfishcode/tool-conventions that referenced this issue Dec 2, 2024
Document the C ABI for `_BitInt`, `_Complex`, `__int128_t`, and
`__uint128_t`. These follow the ABI currently used by clang, to the
best of my knowledge.

Fixes WebAssembly#239.
@sunfishcode
Copy link
Member

I've now filed #240 to document _BitInt and a few other types.

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 a pull request may close this issue.

2 participants