rdar://119382681 Currently, we make the call for whether packed and compact pointer representations are usable based on the global EFFECTIVE_ADDRESS_WIDTH constant; instead, it might be desirable for us move towards finer-grained enablement of these optimizations, specifically being able to enable them on a type-by-type basis. As a first step, let's: - Require types to opt-into compact pointer usage, instead of assuming all pointers can be compacted/packed in the same way. - Add alternate allocator paths for types that are used in compact pointers, giving us a new API point to control how they are allocated in the future.
Pull request: https://github.com/WebKit/WebKit/pull/21517
Committed 271796@main (27959d8049ad): <https://commits.webkit.org/271796@main> Reviewed commits have been landed. Closing PR #21517 and removing active labels.
Re-opened since this is blocked by bug 266140
Pull request: https://github.com/WebKit/WebKit/pull/21576
Committed 271819@main (2c04bdef5846): <https://commits.webkit.org/271819@main> Reviewed commits have been landed. Closing PR #21576 and removing active labels.