Comment #14 on issue 246 by [email protected]: Porting to a new target
(AArch64)
https://code.google.com/p/address-sanitizer/issues/detail?id=246
So, if we keep using Allocator32, that would supposedly mean we have to
revert the
// The range of addresses which can be returned my mmap.
// FIXME: this value should be different on different platforms,
// e.g. on AArch64 it is most likely (1ULL << 39). Larger values will still
work
// but will consume more memory for TwoLevelByteMap.
#if defined(__aarch64__)
# define SANITIZER_MMAP_RANGE_SIZE FIRST_32_SECOND_64(1ULL << 32, 1ULL <<
39)
#else
# define SANITIZER_MMAP_RANGE_SIZE FIRST_32_SECOND_64(1ULL << 32, 1ULL <<
47)
#endif
change and use 1ULL << 47 even on aarch64? What implications does it have
exactly (i.e. how much more memory it will consume?).
Or, what is the minimum usable size for Allocator64? In case of 39-bit
address space it is tight and we definitely can't find terrabytes of memory
anywhere. 42-bit and 47-bit AS has space for it, but the question is if
the space will be always at the same base.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
