[Samsung Galaxy Nexus] metalspring:
Speaking of cflags (and a little back on topic lol), [MENTION=4608636]bsmitty83[/MENTION] would there be much benefit to trying to use fstrict-aliasing cflags in the kernel or would it need too many workarounds?

FYI, to anyone that doesnt know, fstrict-aliasing is one of the cflags used in highly optimized roms (such as vanir) that requires tons and tons of workarounds and fixes to compile and work... actually compiling roms with -03 without fstrict-aliasing on the google toolchains doesnt really require any patches at all (not sure about linaro though), adding fstrict-aliasing means adding anywhere from 30-50 commits or more to make it work lol

Edit: well it looks like some things would need fixed to use strict-aliasing, errored out in about 2 seconds lol

In file included from include/linux/rwsem.h:41:0,

from include/linux/mm_types.h:11,

from include/linux/sched.h:64,

from arch/arm/kernel/asm-offsets.c:13:

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h: In function ‘__down_read’:

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h:43:2: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h: In function ‘__down_write’:

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h:68:5: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h: In function ‘__up_read’:

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h:89:2: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h: In function ‘__up_write’:

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h:100:10: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h: In function ‘rwsem_atomic_add’:

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h:109:2: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h: In function ‘__downgrade_write’:

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h:119:2: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h: In function ‘rwsem_atomic_update’:

/home/metalspring/android/tuna/arch/arm/include/asm/rwsem.h:134:2: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]

In file included from include/linux/aio.h:5:0,

from include/linux/sched.h:386,

from arch/arm/kernel/asm-offsets.c:13:

include/linux/workqueue.h: In function ‘cancel_delayed_work’:

include/linux/workqueue.h:400:3: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]

include/linux/workqueue.h: In function ‘__cancel_delayed_work’:

include/linux/workqueue.h:415:3: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]

cc1: some warnings being treated as errors

make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1