freebsd-dev/sys/boot/efi/Makefile.inc

# $FreeBSD$

BINDIR?=	/boot

.if ${MACHINE_CPUARCH} == "i386"
CFLAGS+=        -march=i386
CFLAGS+=	-mno-aes
.endif

# Options used when building app-specific efi components
# See conf/kern.mk for the correct set of these
CFLAGS+=	-ffreestanding -Wformat -msoft-float ${CFLAGS_NO_SIMD}
LDFLAGS+=	-nostdlib

.if ${MACHINE_CPUARCH} == "amd64"
CFLAGS+=	-fshort-wchar
CFLAGS+=	-mno-red-zone
CFLAGS+=	-mno-aes
.endif

.include "../Makefile.inc"
First approximation of an ia64 EFI loader. Not functional. 2001-06-09 16:49:51 +00:00			`# $FreeBSD$`
style police 2001-06-16 05:59:45 +00:00
Tidy up makefiles. Tested by: marcel 2004-02-12 08:10:34 +00:00			`BINDIR?= /boot`

Don't force efi to a 32-bit build on amd64 Sponsored by: The FreeBSD Foundation 2014-02-07 16:28:40 +00:00			`.if ${MACHINE_CPUARCH} == "i386"`
boot: use -march=i386 for both i386 and amd64 builds .. so that consistent compilation algorithms are used for both architectures as in practice the binaries are expected to be interchangeable (for time being). Previously i386 used default setting which were equivalent to -march=i486 -mtune=generic. The only difference is using smaller but slower "leave" instructions. Discussed with: jhb, dim MFC after: 29 days 2012-10-20 16:57:23 +00:00			`CFLAGS+= -march=i386`
Use CFLAGS_NO_SIMD in preference to varying lists of -mno-xxxx flags. Go ahead and defined -D_STANDALONE for all targets (only strictly needed for some architecture, but harmless on those it isn't required for). Also add -msoft-float to all architectures uniformly rather that higgley piggley like it is today. Differential Revision: https://reviews.freebsd.org/D3496 2015-08-27 23:46:42 +00:00			`CFLAGS+= -mno-aes`
boot: use -march=i386 for both i386 and amd64 builds .. so that consistent compilation algorithms are used for both architectures as in practice the binaries are expected to be interchangeable (for time being). Previously i386 used default setting which were equivalent to -march=i486 -mtune=generic. The only difference is using smaller but slower "leave" instructions. Discussed with: jhb, dim MFC after: 29 days 2012-10-20 16:57:23 +00:00			`.endif`

First approximation of an ia64 EFI loader. Not functional. 2001-06-09 16:49:51 +00:00			`# Options used when building app-specific efi components`
Move the efi loaders to be under sys/boot/efi. This will help us add support for booting arm and arm64 from UEFI. Differential Revision: https://reviews.freebsd.org/D2164 Reviewed by: emaste, imp (previous version) Sponsored by: The FreeBSD Foundation 2015-04-01 08:30:40 +00:00			`# See conf/kern.mk for the correct set of these`
Use CFLAGS_NO_SIMD in preference to varying lists of -mno-xxxx flags. Go ahead and defined -D_STANDALONE for all targets (only strictly needed for some architecture, but harmless on those it isn't required for). Also add -msoft-float to all architectures uniformly rather that higgley piggley like it is today. Differential Revision: https://reviews.freebsd.org/D3496 2015-08-27 23:46:42 +00:00			`CFLAGS+= -ffreestanding -Wformat -msoft-float ${CFLAGS_NO_SIMD}`
Tidy up makefiles. Tested by: marcel 2004-02-12 08:10:34 +00:00			`LDFLAGS+= -nostdlib`
Enable GCC stack protection (aka Propolice) for userland: - It is opt-out for now so as to give it maximum testing, but it may be turned opt-in for stable branches depending on the consensus. You can turn it off with WITHOUT_SSP. - WITHOUT_SSP was previously used to disable the build of GNU libssp. It is harmless to steal the knob as SSP symbols have been provided by libc for a long time, GNU libssp should not have been much used. - SSP is disabled in a few corners such as system bootstrap programs (sys/boot), process bootstrap code (rtld, csu) and SSP symbols themselves. - It should be safe to use -fstack-protector-all to build world, however libc will be automatically downgraded to -fstack-protector because it breaks rtld otherwise. - This option is unavailable on ia64. Enable GCC stack protection (aka Propolice) for kernel: - It is opt-out for now so as to give it maximum testing. - Do not compile your kernel with -fstack-protector-all, it won't work. Submitted by: Jeremie Le Hen <jeremie@le-hen.org> 2008-06-25 21:33:28 +00:00
Clean up more x86 only options in the efi code. 2015-04-03 15:25:59 +00:00			`.if ${MACHINE_CPUARCH} == "amd64"`
			`CFLAGS+= -fshort-wchar`
			`CFLAGS+= -mno-red-zone`
Use CFLAGS_NO_SIMD in preference to varying lists of -mno-xxxx flags. Go ahead and defined -D_STANDALONE for all targets (only strictly needed for some architecture, but harmless on those it isn't required for). Also add -msoft-float to all architectures uniformly rather that higgley piggley like it is today. Differential Revision: https://reviews.freebsd.org/D3496 2015-08-27 23:46:42 +00:00			`CFLAGS+= -mno-aes`
Clean up more x86 only options in the efi code. 2015-04-03 15:25:59 +00:00			`.endif`

Enable GCC stack protection (aka Propolice) for userland: - It is opt-out for now so as to give it maximum testing, but it may be turned opt-in for stable branches depending on the consensus. You can turn it off with WITHOUT_SSP. - WITHOUT_SSP was previously used to disable the build of GNU libssp. It is harmless to steal the knob as SSP symbols have been provided by libc for a long time, GNU libssp should not have been much used. - SSP is disabled in a few corners such as system bootstrap programs (sys/boot), process bootstrap code (rtld, csu) and SSP symbols themselves. - It should be safe to use -fstack-protector-all to build world, however libc will be automatically downgraded to -fstack-protector because it breaks rtld otherwise. - This option is unavailable on ia64. Enable GCC stack protection (aka Propolice) for kernel: - It is opt-out for now so as to give it maximum testing. - Do not compile your kernel with -fstack-protector-all, it won't work. Submitted by: Jeremie Le Hen <jeremie@le-hen.org> 2008-06-25 21:33:28 +00:00			`.include "../Makefile.inc"`