This has been attached to bug 25663 for a bit now, but didn't get
reviewed here. It seems like a smarter way to go about setting up
the CPU_TO_LE32 macro, because it should do a correct but potentially
suboptimal thing on platforms we don't know about (instead of breaking
the build).
-tom
From
tom fogal wrote:
This has been attached to bug 25663 for a bit now, but didn't get
reviewed here. It seems like a smarter way to go about setting up
the CPU_TO_LE32 macro, because it should do a correct but potentially
suboptimal thing on platforms we don't know about (instead of breaking