diff options
| -rw-r--r-- | package/Makefile.in | 4 | ||||
| -rw-r--r-- | package/gcc/gcc.mk | 6 |
2 files changed, 5 insertions, 5 deletions
diff --git a/package/Makefile.in b/package/Makefile.in index 7dc0eac8ce..8a592d4f59 100644 --- a/package/Makefile.in +++ b/package/Makefile.in @@ -91,7 +91,7 @@ endif # code size and performance, the linker can usually optimize away the # overhead when a call ends up within a certain range. # -# Use text-section-literals for Xtensa globally. +# Use auto-litpools for Xtensa globally. # Collecting literals into separate section can be advantageous if that # section is placed into DTCM at link time. This is applicable for code # running on bare metal, but makes no sense under linux, where userspace @@ -100,7 +100,7 @@ endif # instruction can only access literals in 256 KBytes range. # ifeq ($(BR2_xtensa),y) -TARGET_ABI += -mlongcalls -mtext-section-literals +TARGET_ABI += -mlongcalls -mauto-litpools endif ifeq ($(BR2_arc)$(BR2_ARC_ATOMIC_EXT),yy) diff --git a/package/gcc/gcc.mk b/package/gcc/gcc.mk index ead3e150c6..9025cdf6f9 100644 --- a/package/gcc/gcc.mk +++ b/package/gcc/gcc.mk @@ -113,11 +113,11 @@ GCC_COMMON_TARGET_CXXFLAGS = $(filter-out -Os,$(GCC_COMMON_TARGET_CXXFLAGS)) endif endif -# Xtensa libgcc can't be built with -mtext-section-literals +# Xtensa libgcc can't be built with -mauto-litpools # because of the trick used to generate .init/.fini sections. ifeq ($(BR2_xtensa),y) -GCC_COMMON_TARGET_CFLAGS = $(filter-out -mtext-section-literals,$(TARGET_CFLAGS)) -GCC_COMMON_TARGET_CXXFLAGS = $(filter-out -mtext-section-literals,$(TARGET_CXXFLAGS)) +GCC_COMMON_TARGET_CFLAGS = $(filter-out -mauto-litpools,$(TARGET_CFLAGS)) +GCC_COMMON_TARGET_CXXFLAGS = $(filter-out -mauto-litpools,$(TARGET_CXXFLAGS)) endif # Propagate options used for target software building to GCC target libs |
