aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/AST/ByteCode/Compiler.cpp
diff options
context:
space:
mode:
authorAlexander Richardson <alexrichardson@google.com>2025-08-08 10:12:39 -0700
committerGitHub <noreply@github.com>2025-08-08 10:12:39 -0700
commit3a4b351ba18492b990b10fe5401c3bbaabcf2f94 (patch)
tree9bf4b95576a9e0eb75741ebf3249627ee43cdd70 /clang/lib/AST/ByteCode/Compiler.cpp
parent90e8c8e7186616241549e7bc62d95b51467a674b (diff)
downloadllvm-3a4b351ba18492b990b10fe5401c3bbaabcf2f94.zip
llvm-3a4b351ba18492b990b10fe5401c3bbaabcf2f94.tar.gz
llvm-3a4b351ba18492b990b10fe5401c3bbaabcf2f94.tar.bz2
[IR] Introduce the `ptrtoaddr` instruction
This introduces a new `ptrtoaddr` instruction which is similar to `ptrtoint` but has two differences: 1) Unlike `ptrtoint`, `ptrtoaddr` does not capture provenance 2) `ptrtoaddr` only extracts (and then extends/truncates) the low index-width bits of the pointer For most architectures, difference 2) does not matter since index (address) width and pointer representation width are the same, but this does make a difference for architectures that have pointers that aren't just plain integer addresses such as AMDGPU fat pointers or CHERI capabilities. This commit introduces textual and bitcode IR support as well as basic code generation, but optimization passes do not handle the new instruction yet so it may result in worse code than using ptrtoint. Follow-up changes will update capture tracking, etc. for the new instruction. RFC: https://discourse.llvm.org/t/clarifiying-the-semantics-of-ptrtoint/83987/54 Reviewed By: nikic Pull Request: https://github.com/llvm/llvm-project/pull/139357
Diffstat (limited to 'clang/lib/AST/ByteCode/Compiler.cpp')
0 files changed, 0 insertions, 0 deletions