22 Nov
2017
22 Nov
'17
3:56 p.m.
Why do we have two sets of unaligned memory access functions?
Good question.
Both have exactly the same implementation, except for the obvious descripancy in the list of arches getting special treatment. Shouldn't we consolidate this to just one copy of the implementation, and a consistent list of arches using raw access (preferrably using the define HANDLES_UNALIGNED_MEMORY_ACCESS which has also been available since antiquity...)?
Sounds like a good idea.