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
In Metadata.h#L68 the most significant byte of the uint32_t metadatum is accessed by interpreting it as an array of uint8_t and indexing it at the fixed index 3.
As the comment in line 75 of the same file points out, this obviously will only work on little endian machines. I am assuming that this means L4 will not work on big endian machines (e.g. IBM's AIX).
Is this the only issue preventing big endian support or are there other parts (e.g. MurmurHash3.cpp) that would also need to be adapted to support big endian?
In Metadata.h#L68 the most significant byte of the
uint32_tmetadatum is accessed by interpreting it as an array ofuint8_tand indexing it at the fixed index3.As the comment in line 75 of the same file points out, this obviously will only work on little endian machines. I am assuming that this means L4 will not work on big endian machines (e.g. IBM's AIX).
Is this the only issue preventing big endian support or are there other parts (e.g. MurmurHash3.cpp) that would also need to be adapted to support big endian?