u-boot/post/lib_powerpc/fpu/Makefile

#
# (C) Copyright 2007
# Wolfgang Denk, DENX Software Engineering, wd@denx.de.
#
# SPDX-License-Identifier:	GPL-2.0+
#

obj-y	+= 20001122-1.o
obj-y	+= 20010114-2.o
obj-y	+= 20010226-1.o
obj-y	+= 980619-1.o
obj-y	+= acc1.o
obj-y	+= compare-fp-1.o
obj-y	+= fpu.o
obj-y	+= mul-subnormal-single-1.o
obj-y	+= darwin-ldouble.o

CFLAGS := $(shell echo $(CFLAGS) | sed s/-msoft-float//)
CFLAGS += -mhard-float -fkeep-inline-functions

$(addprefix $(obj)/,$(obj-y)): $(obj)/%.o: $(src)/%.c
	$(CC)  $(ALL_CFLAGS) -o $@.fp $< -c
	$(OBJCOPY) -R .gnu.attributes $@.fp $@
	rm -f $@.fp
Merged POST framework with the current TOT. Signed-off-by: Sergei Poselenov <sposelenov@emcraft.com> 18 years ago			`#`
			`# (C) Copyright 2007`
			`# Wolfgang Denk, DENX Software Engineering, wd@denx.de.`
			`#`
Add GPL-2.0+ SPDX-License-Identifier to source files Signed-off-by: Wolfgang Denk <wd@denx.de> [trini: Fixup common/cmd_io.c] Signed-off-by: Tom Rini <trini@ti.com> 12 years ago			`# SPDX-License-Identifier: GPL-2.0+`
Merged POST framework with the current TOT. Signed-off-by: Sergei Poselenov <sposelenov@emcraft.com> 18 years ago			`#`

post: descend only when CONFIG_HAS_POST is defined All objects under post/ directory are enabled by CONFIG_HAS_POST. (post/tests.o is enabled by CONFIG_POST_STD_LIST. But CONFIG_POST_STD_LIST depends on CONFIG_HAS_POST.) We can move CONFIG_HAS_POST switch to the top Makefile. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> 11 years ago			`obj-y += 20001122-1.o`
			`obj-y += 20010114-2.o`
			`obj-y += 20010226-1.o`
			`obj-y += 980619-1.o`
			`obj-y += acc1.o`
			`obj-y += compare-fp-1.o`
			`obj-y += fpu.o`
			`obj-y += mul-subnormal-single-1.o`
			`obj-y += darwin-ldouble.o`
Merged POST framework with the current TOT. Signed-off-by: Sergei Poselenov <sposelenov@emcraft.com> 18 years ago
FPU POST: fix warnings when building with 2.18 binutils When compile u-boot with the 2.18 binutils the following warning messages for each object file in post/lib_ppc/fpu/ is produced at the linking stage: post/libpost.a(acc1.o) uses hard float, u-boot uses soft-float ... This is because of the fact that, in general, the soft-float and hard-float ABIs are incompatible; the 2.18 binutils do checking of the Tag_GNU_Power_ABI_FP attribute of the files to be linked, and produce the worning like above if these are not compatible. The incompatibility of ABIs is concerned only the float values: e.g. the soft-float ABI assumes the float argument passing in the pair of rX registers, and the hard-float ABI assumes passing of the float argument in the fX register. When we don't pass the float arguments between the functions compiled with different floatness, then such an application will work correctly. This is the case for the FPU POST: u-boot (compiled with soft-float) doesn't pass to (and doesn't get from) the FPU POST functions any floats; there are no functions exported from the post/lib_ppc/fpu/ objects which would work with float parameters/returns too. So, we can reassure the linker not to worry about the difference in ABI attributes of linking files just by setting the 'soft-float' attribute for the objects in post/lib_ppc/fpu. And this patch does this. Also, to avoid passing both soft- and hard-float options in CFLAGS when compiling the files from post/lib_ppc/fpu (which is OK, but looks rather dirty) this patch removes the soft-float string from CFLAGS in post/lib_ppc/fpu/Makefile. Signed-off-by: Yuri Tikhonov <yur@emcraft.com> 16 years ago			`CFLAGS := $(shell echo $(CFLAGS) \| sed s/-msoft-float//)`
Merged POST framework with the current TOT. Signed-off-by: Sergei Poselenov <sposelenov@emcraft.com> 18 years ago			`CFLAGS += -mhard-float -fkeep-inline-functions`
PPC: fix "Warning: FOO uses hard float, BAR uses soft float". It appears that with recent versions of GCC the explicit "-mhard-float" command line option takes precedence over the ``asm(".gnu_attribute 4, 2");'' in the source file, so this no longer helps to avoid the warnings we get when linking code that uses FP instructions with other code that was built using soft-float. We can remove the ".gnu_attribute" (which appears to carry no other information, at least so far) from the object files, but we also have to make sure we don't pull in the __gcc_qsub() and __gcc_qmul() functions from the standard libgcc, as these would again "infect" our linking. We copy this code from: gcc-4.2.2/gcc/config/rs6000/darwin-ldouble.c This old version was chosen because it was still available under a compatible license (GCC v2+). The file was stripped down to the needed parts, and reformatted so it passes checkpatch with only one warning (do not add new typedefs). Signed-off-by: Wolfgang Denk <wd@denx.de> Cc: Kumar Gala <galak@kernel.crashing.org> Cc: Stefan Roese <sr@denx.de> Cc: Andy Fleming <afleming@gmail.com> Cc: Kim Phillips <kim.phillips@freescale.com> Tested-by: Stefan Roese <sr@denx.de> Tested-by: Anatolij Gustschin <agust@denx.de> 13 years ago
kbuild: change out-of-tree build This commit changes the working directory where the build process occurs. Before this commit, build process occurred under the source tree for both in-tree and out-of-tree build. That's why we needed to add $(obj) prefix to all generated files in makefiles like follows: $(obj)u-boot.bin: $(obj)u-boot Here, $(obj) is empty for in-tree build, whereas it points to the output directory for out-of-tree build. And our old build system changes the current working directory with "make -C <sub-dir>" syntax when descending into the sub-directories. On the other hand, Kbuild uses a different idea to handle out-of-tree build and directory descending. The build process of Kbuild always occurs under the output tree. When "O=dir/to/store/output/files" is given, the build system changes the current working directory to that directory and restarts the make. Kbuild uses "make -f $(srctree)/scripts/Makefile.build obj=<sub-dir>" syntax for descending into sub-directories. (We can write it like "make $(obj)=<sub-dir>" with a shorthand.) This means the current working directory is always the top of the output directory. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Tested-by: Gerhard Sittig <gsi@denx.de> 11 years ago			`$(addprefix $(obj)/,$(obj-y)): $(obj)/%.o: $(src)/%.c`
PPC: fix "Warning: FOO uses hard float, BAR uses soft float". It appears that with recent versions of GCC the explicit "-mhard-float" command line option takes precedence over the ``asm(".gnu_attribute 4, 2");'' in the source file, so this no longer helps to avoid the warnings we get when linking code that uses FP instructions with other code that was built using soft-float. We can remove the ".gnu_attribute" (which appears to carry no other information, at least so far) from the object files, but we also have to make sure we don't pull in the __gcc_qsub() and __gcc_qmul() functions from the standard libgcc, as these would again "infect" our linking. We copy this code from: gcc-4.2.2/gcc/config/rs6000/darwin-ldouble.c This old version was chosen because it was still available under a compatible license (GCC v2+). The file was stripped down to the needed parts, and reformatted so it passes checkpatch with only one warning (do not add new typedefs). Signed-off-by: Wolfgang Denk <wd@denx.de> Cc: Kumar Gala <galak@kernel.crashing.org> Cc: Stefan Roese <sr@denx.de> Cc: Andy Fleming <afleming@gmail.com> Cc: Kim Phillips <kim.phillips@freescale.com> Tested-by: Stefan Roese <sr@denx.de> Tested-by: Anatolij Gustschin <agust@denx.de> 13 years ago			`$(CC) $(ALL_CFLAGS) -o $@.fp $< -c`
			`$(OBJCOPY) -R .gnu.attributes $@.fp $@`
			`rm -f $@.fp`