backend/address_space: drop spurious !StrictProvenance guard
This dates back to the much earlier design that required the use of an authority map. Since the current CHERI design does not, go ahead and ask the platform whenever underlying allocation requests are sufficiently aligned.
This commit is contained in:
committed by
Nathaniel Wesley Filardo
parent
3cdb7be478
commit
8023a6c906
@@ -53,12 +53,10 @@ namespace snmalloc
|
||||
SNMALLOC_ASSERT(size >= sizeof(void*));
|
||||
|
||||
/*
|
||||
* For sufficiently large allocations with platforms that support
|
||||
* aligned allocations and architectures that don't require
|
||||
* StrictProvenance, try asking the platform first.
|
||||
* For sufficiently large allocations with platforms that support aligned
|
||||
* allocations, try asking the platform directly.
|
||||
*/
|
||||
if constexpr (
|
||||
pal_supports<AlignedAllocation, PAL> && !aal_supports<StrictProvenance>)
|
||||
if constexpr (pal_supports<AlignedAllocation, PAL>)
|
||||
{
|
||||
if (size >= PAL::minimum_alloc_size)
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user