[PATCH] unaligned: write in increasing memory order

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This ordering seems more logical.

Signed-off-by: Harvey Harrison <harvey.harrison@xxxxxxxxx>
---
gcc 4.2 seems to be smart enough to figure it out in either order.

 include/asm-generic/unaligned.h |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/asm-generic/unaligned.h b/include/asm-generic/unaligned.h
index 3bef59f..55d1126 100644
--- a/include/asm-generic/unaligned.h
+++ b/include/asm-generic/unaligned.h
@@ -164,14 +164,14 @@ static inline void __put_le16_noalign(u8 *p, u16 val)
 
 static inline void __put_le32_noalign(u8 *p, u32 val)
 {
-	__put_le16_noalign(p + 2, val >> 16);
 	__put_le16_noalign(p, val);
+	__put_le16_noalign(p + 2, val >> 16);
 }
 
 static inline void __put_le64_noalign(u8 *p, u64 val)
 {
-	__put_le32_noalign(p + 4, val >> 32);
 	__put_le32_noalign(p, val);
+	__put_le32_noalign(p + 4, val >> 32);
 }
 
 static inline void __put_be16_noalign(u8 *p, u16 val)
-- 
1.6.0.4.1013.gc6a01



--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux