Skip to content

Conversation

@kingiler
Copy link
Contributor

Your checklist for this pull request

  • I've documented or updated the documentation of every API function and struct this PR changes.
  • I've added tests that prove my fix is effective or that my feature works (if possible)

Detailed description

On systems such as CHERI which distinguish integers and pointers, uintptr_t should be used to prevent pointer provenance issues.
The fix allows capstone to be compiled and run on ARM Morello.

...

Test plan

N/A.

If a physical CHERI machine is not available, one can use cheribuild to build QEMU for Morello and CHERI-RISC-V and run code inside it.

...

Closing issues

N/A

...

@github-actions github-actions bot added the CS-core-files auto-sync label Jan 10, 2026
@kingiler kingiler marked this pull request as ready for review January 10, 2026 05:28
@kingiler kingiler changed the title Use uintptr_t to maintain pointer provenance. fix: use uintptr_t to maintain pointer provenance Jan 10, 2026
Copy link
Collaborator

@Rot127 Rot127 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kingiler kingiler requested review from Rot127 and jiegec January 11, 2026 02:08
@kingiler
Copy link
Contributor Author

Where should I add a note in the release guide? Should it be in Breaking changes/General?

@Rot127
Copy link
Collaborator

Rot127 commented Jan 11, 2026

I think it could go under Code quality. Since it s not really a breaking change

@Rot127
Copy link
Collaborator

Rot127 commented Jan 12, 2026

Never mind. I'll add it to the docs.

@Rot127 Rot127 merged commit 42225ea into capstone-engine:next Jan 12, 2026
27 checks passed
@Rot127 Rot127 mentioned this pull request Jan 12, 2026
2 tasks
@kingiler kingiler deleted the uintptr branch January 13, 2026 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CS-core-files auto-sync

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants