tree 36fb9dc1dd61310f92f4010ccd30d03aabd65709
parent e620f10f57bf698b7446f134528bb2585fdf1f28
author Alexander Richardson <alexrichardson@google.com> 1747415040 -0700
committer GitHub <noreply@github.com> 1747415040 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJoJ3AACRC1aQ7uu5UhlAAAFUwQAEVkknIPowoC62zUUpHXLps2
 vNt0M4Om0XkAkn2vFdTFLWs8blAWhA1/klVJqxabYlEGNoCQnrdyAF4Cevw6/6/G
 Po003ZCFka463ovfaCFtlzPXKl5nkjaZCeGuiWnG0TfSVaHCAii0yvGeQ23JPUMj
 farIBt+6sjkmSL8CYwCJfIoBB7J1KkKLdQydki5VLgouc+PZyaEZXDiXfDVcX994
 cSiX+6237PSTNifsGAZZU3MzmQFI4lP19q3wGjPjdgW9L+uMHiZRN8NVATpa11Ad
 2mk+n1ilptxnbU7rcFRX8wlDRrKk0vISp3ceISRfl3M072tsDISEQeRLnzRP0EwF
 sSzXH3A0Cy2qvGe5LCn6Dvgn5RaQWKKolyNJbzrWLcyaebZ+mj/eaP6uRgh3gGVC
 220ewrULtFcZ7QJgIQkhiFfAkyyROzYYii8Zo3t9/TTJ9w3Aj7WUih9FVwZT2UPN
 dZwVUlfrKodr7cVNb10QMAXr4F2jNeXeW4Zss9uON5Njt4ZTjYpheDCUM0x5oOhl
 nkH0RYNb23OULlk9An+cmp0ykWZil+EJT1wGGR3JP/8U5m6Zz72JaKTsUYHdPAav
 baGa8kR4mpf7z9AanOzxjTfvriWniZcOWVGN8/Taplii2BPYF0F5GmiGS1zWWaZf
 xghOScoe6MLNCj6hwcQn
 =LTUv
 -----END PGP SIGNATURE-----
 

[DataLayout] Introduce DataLayout::getAddressSize(AS)

This function can be used to retrieve the number of bits that can be used
for arithmetic in a given address space (i.e. the range of the address
space). For most in-tree targets this should not make any difference
but differentiating between the size of a pointer in bits and the address
range is extremely important e.g. for CHERI-enabled targets, where pointers
carry additional metadata such as bounds and permissions and only a subset
of the pointer bits is used as the address.

The address size is defined to be the same as the index size.

We considered adding a separate property since targets exist where indexing
and address range actually use different sizes (AMDGPU fat pointers with
160 representation, 48 bit address and 32 bit index), but for the purposes
of LLVM semantics, differentiating them does not add much value and it
introduces a lot of complexity in ensure the correct bits are used. See
the reasoning by @nikic on https://discourse.llvm.org/t/clarifiying-the-semantics-of-ptrtoint/83987/38https://discourse.llvm.org/t/clarifiying-the-semantics-of-ptrtoint/83987/49

Originally uploaded as https://reviews.llvm.org/D135158

Reviewed By: davidchisnall, krzysz00

Pull Request: https://github.com/llvm/llvm-project/pull/139347