Skip to content

Conversation

@xlauko
Copy link
Collaborator

@xlauko xlauko commented May 7, 2025

  • Rename PrimitiveIntOrFPPtr to CIR_PtrToIntOrFloatType and broaden it to accept any floating-point type.
  • Fix incorrect constraint name from PrimitiveInt to any Int; prior constraint already allowed arbitrary bitwidths, so the name was misleading.
  • Rename ComplexPtr to CIR_PtrToComplexType for clarity.

- Rename `PrimitiveIntOrFPPtr` to `CIR_PtrToIntOrFloatType` and broaden it to accept any floating-point type.
- Fix incorrect constraint change from `PrimitiveInt` to `Int`; prior constraint already allowed arbitrary bitwidths, so the name was misleading.
- Rename `ComplexPtr` to `CIR_PtrToComplexType` for clarity.
@xlauko xlauko marked this pull request as ready for review May 7, 2025 20:19
@xlauko xlauko requested review from bcardosolopes and lanza as code owners May 7, 2025 20:19
@xlauko
Copy link
Collaborator Author

xlauko commented May 7, 2025

This stack of pull requests is managed by Graphite. Learn more about stacking.

@bcardosolopes bcardosolopes merged commit 2a034be into main May 7, 2025
12 checks passed
@xlauko xlauko deleted the users/xlauko/cir-scalar-ptr-constraints branch June 5, 2025 20:09
terapines-osc-cir pushed a commit to Terapines/clangir that referenced this pull request Sep 2, 2025
…llvm#1605)

- Rename `PrimitiveIntOrFPPtr` to `CIR_PtrToIntOrFloatType` and broaden
it to accept any floating-point type.
- Fix incorrect constraint name from `PrimitiveInt` to any `Int`; prior
constraint already allowed arbitrary bitwidths, so the name was
misleading.
- Rename `ComplexPtr` to `CIR_PtrToComplexType` for clarity.
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.

3 participants