From: Sam Ravnborg <sam@xxxxxxxxxxxx> Date: Tue, 27 Dec 2011 22:28:50 +0100 >>From 8d3ccd703b99564b119a6ddb4127c31f8f2fece3 Mon Sep 17 00:00:00 2001 > From: Sam Ravnborg <sam@xxxxxxxxxxxx> > Date: Tue, 27 Dec 2011 21:46:53 +0100 > Subject: [PATCH] sparc32: support atomic64_t > > There is no-one that really require atomic64_t support on sparc32. > But several drivers fails to build without proper atomic64 support. > And for an allyesconfig build for sparc32 this is annoying. > > Include the generic atomic64_t support for sparc32. > This has a text footprint cost: > > $size vmlinux (before atomic64_t support) > text data bss dec hex filename > 3578860 134260 108781 3821901 3a514d vmlinux > > $size vmlinux (after atomic64_t support) > text data bss dec hex filename > 3579892 130684 108781 3819357 3a475d vmlinux > > text increase (3579892 - 3578860) = 1032 bytes > > data decreases - but I fail to explain why! > I have rebuild twice to check my numbers. > > Signed-off-by: Sam Ravnborg <sam@xxxxxxxxxxxx> Applied to sparc-next, thanks. The data decreasing is really funny indeed, it should increase because of the atomic64_lock[] array in lib/atomic64.c And the decrease isn't some trivial amount, it's more than 3K! -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
