diff options
author | Nikita Popov <npopov@redhat.com> | 2025-10-02 09:16:08 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-10-02 09:16:08 +0200 |
commit | a4767e63eebfa1ae0065bdd8813df3839f62b461 (patch) | |
tree | c4fbcaaf9d34d440e14d6a8c9dd508c0ea1324ef /lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp | |
parent | 912a92a8098a425c63be3cf3251f3cab68d229c4 (diff) | |
download | llvm-a4767e63eebfa1ae0065bdd8813df3839f62b461.zip llvm-a4767e63eebfa1ae0065bdd8813df3839f62b461.tar.gz llvm-a4767e63eebfa1ae0065bdd8813df3839f62b461.tar.bz2 |
[MemorySanitizer] Use getelementptr instead of ptrtoint+add+inttoptr (#161392)
MemorySanitizer currently does a lot of pointer arithmetic using
ptrtoint+add+inttoptr instead of using getelementptr. As far as I can
tell, there is no need to use this pattern -- msan is not trying to
synthesize pointers with different provenance here. The pointers in
question stay within one object (like the TLS parameter area).
I suspect that this is just a leftover from pre-opaque-pointer types
where this was a natural way to perform offset arithmetic. Nowadays we
should just emit a getelementptr i8, aka ptradd.
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp')
0 files changed, 0 insertions, 0 deletions