Stop asking GCC to cause trouble.
Why do we see so many bogus strict-aliasing warnings? Because we asked GCC to cause trouble on arm and mips. Change-Id: I25d7fd036b6afff7ccfa799abe0dc1579ead2847
This commit is contained in:
parent
26172fa401
commit
b8dc9bbd90
@ -41,10 +41,7 @@ libc_common_src_files_arm += \
|
||||
# bionic/__strcpy_chk.cpp \
|
||||
# bionic/__strcat_chk.cpp \
|
||||
|
||||
# cflags
|
||||
libc_common_cflags_arm := \
|
||||
-DSOFTFLOAT \
|
||||
-fstrict-aliasing
|
||||
libc_common_cflags_arm := -DSOFTFLOAT
|
||||
|
||||
##########################################
|
||||
### CPU specific source files
|
||||
|
@ -43,13 +43,10 @@ libc_common_src_files_mips += \
|
||||
bionic/__strcat_chk.cpp \
|
||||
|
||||
|
||||
# cflags
|
||||
ifneq ($(ARCH_MIPS_HAS_FPU),true)
|
||||
libc_common_cflags_mips := \
|
||||
-DSOFTFLOAT
|
||||
endif
|
||||
libc_common_cflags_mips += \
|
||||
-fstrict-aliasing
|
||||
|
||||
##########################################
|
||||
### CPU specific source files
|
||||
|
Loading…
x
Reference in New Issue
Block a user