That’s what we do in CHERI. For allocation-bounded things it’s totally fine. The rounding that an allocator does of size classes is far coarser than we require. It can be annoying enforcing sub-object bounds, particularly if you want something like a slice type: we can’t represent an arbitrary range of a very large array. You won’t hit this unless you’re doing sub-object bounds for multi-MiB objects on a 64-bit system, but it can be annoying for things like separate capabilities for header and data in an encoded video frame.
That’s what we do in CHERI. For allocation-bounded things it’s totally fine. The rounding that an allocator does of size classes is far coarser than we require. It can be annoying enforcing sub-object bounds, particularly if you want something like a slice type: we can’t represent an arbitrary range of a very large array. You won’t hit this unless you’re doing sub-object bounds for multi-MiB objects on a 64-bit system, but it can be annoying for things like separate capabilities for header and data in an encoded video frame.
score 2 · canonical