|
|
|
|
#
|
|
|
|
|
# (C) Copyright 2002-2006
|
|
|
|
|
# Wolfgang Denk, DENX Software Engineering, wd@denx.de.
|
|
|
|
|
#
|
|
|
|
|
# SPDX-License-Identifier: GPL-2.0+
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
include $(TOPDIR)/config.mk
|
|
|
|
|
|
|
|
|
|
LIB = $(obj)lib$(ARCH).o
|
|
|
|
|
|
|
|
|
|
COBJS-$(CONFIG_CMD_BOOTM) += bootm.o
|
|
|
|
|
COBJS-y += cmd_boot.o
|
x86: Wrap small helper functions from libgcc to avoid an ABI mismatch
When gcc compiles some 64 bit operations on a 32 bit machine, it generates
calls to small functions instead of instructions which do the job directly.
Those functions are defined in libgcc and transparently provide whatever
functionality was necessary. Unfortunately, u-boot can be built with a
non-standard ABI when libgcc isn't. More specifically, u-boot uses
-mregparm. When the u-boot and libgcc are linked together, very confusing
bugs can crop up, for instance seemingly normal integer division or modulus
getting the wrong answer or even raising a spurious divide by zero
exception.
This change borrows (steals) a technique and some code from coreboot which
solves this problem by creating wrappers which translate the calling
convention when calling the functions in libgcc. Unfortunately that means
that these instructions which had already been turned into functions have
even more overhead, but more importantly it makes them work properly.
To find all of the functions that needed wrapping, u-boot was compiled
without linking in libgcc. All the symbols the linker complained were
undefined were presumed to be the symbols that are needed from libgcc.
These were a subset of the symbols covered by the coreboot code, so it was
used unmodified.
To prevent symbols which are provided by libgcc but not currently wrapped
(or even known about) from being silently linked against by code generated
by libgcc, a new copy of libgcc is created where all the symbols are
prefixed with __normal_. Without being purposefully wrapped, these symbols
will cause linker errors instead of silently introducing very subtle,
confusing bugs.
Another approach would be to whitelist symbols from libgcc and strip out
all the others. The problem with this approach is that it requires the
white listed symbols to be specified three times, once for objcopy, once so
the linker inserts the wrapped, and once to generate the wrapper itself,
while this implementation needs it to be listed only twice. There isn't
much tangible difference in what each approach produces, so this one was
preferred.
Signed-off-by: Gabe Black <gabeblack@chromium.org>
13 years ago
|
|
|
COBJS-y += gcc.o
|
|
|
|
|
COBJS-y += init_helpers.o
|
|
|
|
|
COBJS-y += interrupts.o
|
|
|
|
|
COBJS-$(CONFIG_SYS_PCAT_INTERRUPTS) += pcat_interrupts.o
|
|
|
|
|
COBJS-$(CONFIG_SYS_PCAT_TIMER) += pcat_timer.o
|
|
|
|
|
COBJS-$(CONFIG_PCI) += pci_type1.o
|
|
|
|
|
COBJS-y += relocate.o
|
|
|
|
|
COBJS-y += physmem.o
|
|
|
|
|
COBJS-y += string.o
|
|
|
|
|
COBJS-$(CONFIG_SYS_X86_TSC_TIMER) += tsc_timer.o
|
|
|
|
|
COBJS-$(CONFIG_VIDEO_VGA) += video.o
|
|
|
|
|
COBJS-$(CONFIG_CMD_ZBOOT) += zimage.o
|
|
|
|
|
|
|
|
|
|
SRCS := $(SOBJS-y:.o=.S) $(COBJS-y:.o=.c)
|
|
|
|
|
OBJS := $(addprefix $(obj),$(SOBJS-y) $(COBJS-y))
|
|
|
|
|
|
|
|
|
|
$(LIB): $(obj).depend $(OBJS)
|
|
|
|
|
$(call cmd_link_o_target, $(OBJS))
|
|
|
|
|
|
x86: Wrap small helper functions from libgcc to avoid an ABI mismatch
When gcc compiles some 64 bit operations on a 32 bit machine, it generates
calls to small functions instead of instructions which do the job directly.
Those functions are defined in libgcc and transparently provide whatever
functionality was necessary. Unfortunately, u-boot can be built with a
non-standard ABI when libgcc isn't. More specifically, u-boot uses
-mregparm. When the u-boot and libgcc are linked together, very confusing
bugs can crop up, for instance seemingly normal integer division or modulus
getting the wrong answer or even raising a spurious divide by zero
exception.
This change borrows (steals) a technique and some code from coreboot which
solves this problem by creating wrappers which translate the calling
convention when calling the functions in libgcc. Unfortunately that means
that these instructions which had already been turned into functions have
even more overhead, but more importantly it makes them work properly.
To find all of the functions that needed wrapping, u-boot was compiled
without linking in libgcc. All the symbols the linker complained were
undefined were presumed to be the symbols that are needed from libgcc.
These were a subset of the symbols covered by the coreboot code, so it was
used unmodified.
To prevent symbols which are provided by libgcc but not currently wrapped
(or even known about) from being silently linked against by code generated
by libgcc, a new copy of libgcc is created where all the symbols are
prefixed with __normal_. Without being purposefully wrapped, these symbols
will cause linker errors instead of silently introducing very subtle,
confusing bugs.
Another approach would be to whitelist symbols from libgcc and strip out
all the others. The problem with this approach is that it requires the
white listed symbols to be specified three times, once for objcopy, once so
the linker inserts the wrapped, and once to generate the wrapper itself,
while this implementation needs it to be listed only twice. There isn't
much tangible difference in what each approach produces, so this one was
preferred.
Signed-off-by: Gabe Black <gabeblack@chromium.org>
13 years ago
|
|
|
$(PREFIXED_LIBGCC): $(NORMAL_LIBGCC)
|
|
|
|
|
$(OBJCOPY) $< $@ --prefix-symbols=__normal_
|
|
|
|
|
|
|
|
|
|
$(LIB): $(PREFIXED_LIBGCC)
|
|
|
|
|
|
|
|
|
|
#########################################################################
|
|
|
|
|
|
|
|
|
|
# defines $(obj).depend target
|
|
|
|
|
include $(SRCTREE)/rules.mk
|
|
|
|
|
|
|
|
|
|
sinclude $(obj).depend
|
|
|
|
|
|
|
|
|
|
#########################################################################
|
