d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
372ef8405c
freebsd-nq/share/mk/bsd.sys.mk

57 lines
1.5 KiB
Makefile
Raw Normal View History

Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
# $FreeBSD$
#
# This file contains common settings used for building FreeBSD
# sources.
# Enable various levels of compiler warning checks. These may be
# overridden (e.g. if using a non-gcc compiler) by defining NO_WARNS.
Gcc 3.1 has different -Wx flags.
2002-05-10 01:58:16 +00:00
# for GCC: http://gcc.gnu.org/onlinedocs/gcc-3.0.4/gcc_3.html#IDX143
This are the build infrastructure changes to allow to use the Intel C/C++ compiler (lang/icc) to build the kernel. The icc CPUTYPE CFLAGS use icc v7 syntax, icc v8 moans about them, but doesn't abort. They also produce CPU specific code (new instructions of the CPU, not only CPU specific scheduling), so if you get coredumps with signal 4 (SIGILL, illegal instruction) you've used the wrong CPUTYPE. Incarnations of this patch survive gcc compiles and my make universe. I use it on my desktop. To use it update share/mk, add /usr/local/intel/compiler70/ia32/bin (icc v7, works) or /usr/local/intel_cc_80/bin (icc v8, doesn't work) to your PATH, make sure you have a new kernel compile directory (e.g. MYKERNEL_icc) and run CFLAGS="-O2 -ip" CC=icc make depend CFLAGS="-O2 -ip" CC=icc make in it. Don't compile with -ipo, the build infrastructure uses ld directly to link the kernel and the modules, but -ipo needs the link step to be performed with Intel's linker. Problems with icc v8: - panic: npx0 cannot be emulated on an SMP system - UP: first start of /bin/sh results in a FP exception Parts of this commit contains suggestions or submissions from Marius Strobl <marius@alchemy.franken.de>. Reviewed by: silence on -arch Submitted by: netchild
2004-03-12 21:36:12 +00:00
.if !defined(NO_WARNS) && ${CC} != "icc"
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. if defined(WARNS)
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 1
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Wsystem-headers
Be more strict with WARNS now -- the GCC 3.1 turmoil is behind us.
2002-07-07 18:47:52 +00:00
. if !defined(NO_WERROR)
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Werror
Be more strict with WARNS now -- the GCC 3.1 turmoil is behind us.
2002-07-07 18:47:52 +00:00
. endif
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. endif
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 2
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Wall -Wno-format-y2k
Add some granularity to the WARNS levels. 1: add -Werror 2: -Wall [only], as this is the most used warnings setting by developers 3: our old `1' 4: our old `2'
2001-12-15 06:02:15 +00:00
. endif
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 3
Move -Wunused-parameter from WARNS level 3 level 4. Also break long lines -- note that the '\' must be up against the last character of a line to keep command-line spacing proper. Requested by: rwatson
2005-01-16 21:18:16 +00:00
CWARNFLAGS += -W -Wno-unused-parameter -Wstrict-prototypes\
-Wmissing-prototypes -Wpointer-arith
Add some granularity to the WARNS levels. 1: add -Werror 2: -Wall [only], as this is the most used warnings setting by developers 3: our old `1' 4: our old `2'
2001-12-15 06:02:15 +00:00
. endif
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 4
Move -Wunused-parameter from WARNS level 3 level 4. Also break long lines -- note that the '\' must be up against the last character of a line to keep command-line spacing proper. Requested by: rwatson
2005-01-16 21:18:16 +00:00
CWARNFLAGS += -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch\
-Wshadow -Wcast-align -Wunused-parameter
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. endif
Add WARNS levels 5 and 6: 5 gives us -Wuninitialized rather than -Wno-uninitialized 6 gives us full BDECFLAGS
2002-04-10 02:45:22 +00:00
# BDECFLAGS
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 6
Remove -Wbad-function-cast. Its main purpose is to catch bugs that we already catch with -Wstrict-prototypes, and it causes spurious warnings for some perfectly legitimate constructs.
2004-02-16 20:07:06 +00:00
CWARNFLAGS += -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
Add WARNS levels 5 and 6: 5 gives us -Wuninitialized rather than -Wno-uninitialized 6 gives us full BDECFLAGS
2002-04-10 02:45:22 +00:00
. endif
Use >= so we can use the actual WARNS levels.
2005-01-16 21:08:31 +00:00
. if ${WARNS} >= 2 && ${WARNS} <= 4
Put -Wno-uninitialized at the end of the warns flags as it may be enabeled by several flags (in this case -W and -Wall). Reviewed by: bde
2002-01-05 20:17:50 +00:00
# XXX Delete -Wuninitialized by default for now -- the compiler doesn't
# XXX always get it right.
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Wno-uninitialized
Put -Wno-uninitialized at the end of the warns flags as it may be enabeled by several flags (in this case -W and -Wall). Reviewed by: bde
2002-01-05 20:17:50 +00:00
. endif
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. endif
. if defined(FORMAT_AUDIT)
WFORMAT = 1
. endif
. if defined(WFORMAT)
. if ${WFORMAT} > 0
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
#CWARNFLAGS += -Wformat-nonliteral -Wformat-security -Wno-format-extra-args
CWARNFLAGS += -Wformat=2 -Wno-format-extra-args
Be more strict with WARNS now -- the GCC 3.1 turmoil is behind us.
2002-07-07 18:47:52 +00:00
. if !defined(NO_WERROR)
Put the warning flags to where they belong (into CWARNFLAGS). This allows us to easily override them when necessary, e.g., to selectively disable warnings in libc/ contributed sources.
2004-01-11 10:29:55 +00:00
CWARNFLAGS += -Werror
Be more strict with WARNS now -- the GCC 3.1 turmoil is behind us.
2002-07-07 18:47:52 +00:00
. endif
Only add -Werror if in fact we have set WARNS or WFORMAT to >0
2001-05-19 23:32:19 +00:00
. endif
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner. The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
2001-05-19 23:18:21 +00:00
. endif
.endif
# Allow user-specified additional warning flags
CFLAGS += ${CWARNFLAGS}
Reference in New Issue Copy Permalink