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

Lack of support on __int128 type #953

Closed
Lancern opened this issue Oct 9, 2024 · 0 comments · Fixed by #980
Closed

Lack of support on __int128 type #953

Lancern opened this issue Oct 9, 2024 · 0 comments · Fixed by #980
Assignees

Comments

@Lancern
Copy link
Member

Lancern commented Oct 9, 2024

Support for the __int128 type is still NYI. Tracking it in this issue.

@Lancern Lancern self-assigned this Oct 9, 2024
bcardosolopes pushed a commit that referenced this issue Oct 16, 2024
This PR adds initial support for the `__int128` type. The `!cir.int`
type is extended to support 128-bit integer types.

This PR comes with a simple test that verifies the CIRGen and LLVM
lowering of `!s128i` and `!u128i` work.

Resolve #953 .
keryell pushed a commit to keryell/clangir that referenced this issue Oct 19, 2024
This PR adds initial support for the `__int128` type. The `!cir.int`
type is extended to support 128-bit integer types.

This PR comes with a simple test that verifies the CIRGen and LLVM
lowering of `!s128i` and `!u128i` work.

Resolve llvm#953 .
bcardosolopes pushed a commit that referenced this issue Oct 31, 2024
This PR adds calling convention lowering support for the int128 type on
x86_64.

This is a follow up on #953 .
lanza pushed a commit that referenced this issue Nov 5, 2024
This PR adds initial support for the `__int128` type. The `!cir.int`
type is extended to support 128-bit integer types.

This PR comes with a simple test that verifies the CIRGen and LLVM
lowering of `!s128i` and `!u128i` work.

Resolve #953 .
lanza pushed a commit that referenced this issue Nov 5, 2024
This PR adds calling convention lowering support for the int128 type on
x86_64.

This is a follow up on #953 .
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.

1 participant