about summary refs log tree commit diff
path: root/aclocal.m4
diff options
context:
space:
mode:
authorSergey Bugaev <bugaevc@gmail.com>2024-03-23 20:32:43 +0300
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2024-03-23 22:44:02 +0100
commit4648bfbbde5466929d24013478697cbdec847b46 (patch)
tree037d73cb252ab69411a871540127e7d4a1f5d1cc /aclocal.m4
parent7f02511e5b8879430e2b3c51601341d3c0314071 (diff)
downloadglibc-4648bfbbde5466929d24013478697cbdec847b46.tar.gz
glibc-4648bfbbde5466929d24013478697cbdec847b46.tar.xz
glibc-4648bfbbde5466929d24013478697cbdec847b46.zip
hurd: Stop relying on VM_MAX_ADDRESS
We'd like to avoid committing to a specific size of virtual address
space (i.e. the value of VM_AARCH64_T0SZ) on AArch64.  While the current
version of GNU Mach still exports VM_MAX_ADDRESS for compatibility, we
should try to avoid relying on it when we can.  This piece of logic in
_hurdsig_getenv () doesn't actually care about the size of user-
accessible virtual address space, it just wants to preempt faults on any
addresses starting from the value of the P pointer and above.  So, use
(unsigned long int) -1 instead of VM_MAX_ADDRESS.

While at it, change the casts to (unsigned long int) and not just
(long int), since the type of struct hurd_signal_preemptor.{first,last}
is unsigned long int.

Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
Message-ID: <20240323173301.151066-3-bugaevc@gmail.com>
Diffstat (limited to 'aclocal.m4')
0 files changed, 0 insertions, 0 deletions