tree 1ab0194da71b7f286696527b4d8ce859063f7dce
parent 2804038343ac6c87717e9fd2a8149b2a64184e88
author Jessica Clarke <jrtc27@jrtc27.com> 1611775700 +0000
committer Copybara-Service <copybara-worker@google.com> 1611865895 -0800

[builtins] Fix integer/pointer confusion in gcc_personality_v0.c

This fixes the implementation for architectures like CHERI with strong
pointer provenance (pointers, and thus uintptr_t, are represented as
hardware capabilities). Specifically, adding two uintptr_t's together
(as is done for `start + length` and `funcStart + landingPad`) has
ambiguous provenance, whereas using a plain integer (such as size_t) for
the offset operand does not. Also, readULEB128 is creating a plain
integer, not a pointer.

On all currently-supported architectures this should be an NFC, as
size_t and uintptr_t end up being the same underlying plain integer
type.

Reviewed By: MaskRay

Differential Revision: https://reviews.llvm.org/D95537

GitOrigin-RevId: 5748a71ba3da69e9f0bfb2024eadfe6eeacade01