Incidentally, HANDLES_UNALIGNED_MEMORY_ACCESS was originally set by a configure test, but this was removed for unknown reasons in 0919be6. We could put it back, although such a test only shows that raw access _works_, not that it is faster than the memcpy variant (it could be handled by a kernel trap).