On Thu, 12 Jan 2023 20:36:31 GMT, Justin King wrote:
>> The implementation of `offset_of` for GCC/Clang only deals with types are
>> aligned to 16 bytes or less, if they are more, such as `zCollectedHeap` the
>> behavior is undefined. UBSan also suggests that `offset_of` is not always a
>> com
On Thu, 12 Jan 2023 20:28:50 GMT, Justin King wrote:
> The implementation of `offset_of` for GCC/Clang only deals with types are
> aligned to 16 bytes or less, if they are more, such as `zCollectedHeap` the
> behavior is undefined. UBSan also suggests that `offset_of` is not always a
> compile
On Thu, 12 Jan 2023 20:28:50 GMT, Justin King wrote:
> The implementation of `offset_of` for GCC/Clang only deals with types are
> aligned to 16 bytes or less, if they are more, such as `zCollectedHeap` the
> behavior is undefined. UBSan also suggests that `offset_of` is not always a
> compile
On Thu, 12 Jan 2023 20:28:50 GMT, Justin King wrote:
> The implementation of `offset_of` for GCC/Clang only deals with types are
> aligned to 16 bytes or less, if they are more, such as `zCollectedHeap` the
> behavior is undefined. UBSan also suggests that `offset_of` is not always a
> compile
On Thu, 12 Jan 2023 20:28:50 GMT, Justin King wrote:
> The implementation of `offset_of` for GCC/Clang only deals with types are
> aligned to 16 bytes or less, if they are more, such as `zCollectedHeap` the
> behavior is undefined. UBSan also suggests that `offset_of` is not always a
> compile
The implementation of `offset_of` for GCC/Clang only deals with types are
aligned to 16 bytes or less, if they are more, such as `zCollectedHeap` the
behavior is undefined. UBSan also suggests that `offset_of` is not always a
compile time constant, as the stack trace came from the dynamic loader
