examples/standalone: Use gcc's -fno-toplevel-reorder
Using -fno-toplevel-reorder causes gcc to not reorder functions. This
ensures that an application's entry point will be the first function in
the application's source file.
This change, along with commit 620bbba524
should cause a standalone application's entry point to be at the base of
the compiled binary. Previously, the entry point could change depending
on gcc version and flags.
Note -fno-toplevel-reorder is only available in gcc version 4.2 or
greater.
Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
This commit is contained in:
parent
92d1a400bc
commit
c91d456c05
|
@ -82,6 +82,11 @@ CFLAGS := $(filter-out $(RELFLAGS),$(CFLAGS))
|
|||
CPPFLAGS := $(filter-out $(RELFLAGS),$(CPPFLAGS))
|
||||
endif
|
||||
|
||||
# We don't want gcc reordering functions if possible. This ensures that an
|
||||
# application's entry point will be the first function in the application's
|
||||
# source file.
|
||||
CFLAGS += $(call cc-option,-fno-toplevel-reorder)
|
||||
|
||||
all: $(obj).depend $(OBJS) $(LIB) $(SREC) $(BIN) $(ELF)
|
||||
|
||||
#########################################################################
|
||||
|
|
Loading…
Reference in New Issue