You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 12, 2022. It is now read-only.
Do not include padding when hashing floating point types
The exact contents of the padding is not specified. Usually
it's 0, but some optimizations in GDC sometimes lead to
different padding content.
For floating point types without padding, the code is unchanged.
For real or imaginary types with padding, just ignore the trailing
padding.
For complex types where the real/imaginary types have padding, we
can't hash the value as one contiguous memory block, as there
will be a padding 'hole'. Here, hash real and imaginary part
individually. Complex types without padding are still hashed
as one memory block.
0 commit comments