1999-08-28 00:22:10 +00:00
|
|
|
# $FreeBSD$
|
1996-10-08 22:10:49 +00:00
|
|
|
|
|
|
|
#
|
|
|
|
# Warning flags for compiling the kernel and components of the kernel.
|
|
|
|
#
|
1999-01-29 10:57:18 +00:00
|
|
|
# Note that the newly added -Wcast-qual is responsible for generating
|
|
|
|
# most of the remaining warnings. Warnings introduced with -Wall will
|
|
|
|
# also pop up, but are easier to fix.
|
|
|
|
#
|
|
|
|
CWARNFLAGS?= -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \
|
|
|
|
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \
|
1998-09-09 10:04:58 +00:00
|
|
|
-fformat-extensions -ansi
|
1999-01-29 10:57:18 +00:00
|
|
|
#
|
|
|
|
# The following flags are next up for working on:
|
|
|
|
# -W
|
|
|
|
#
|
|
|
|
# When working on removing warnings from code, the `-Werror' flag should be
|
|
|
|
# of material assistance.
|
|
|
|
#
|
1999-01-27 22:53:58 +00:00
|
|
|
|
1999-11-17 07:30:35 +00:00
|
|
|
#
|
|
|
|
# On the i386, do not align the stack to 16-byte boundaries. Otherwise GCC
|
|
|
|
# 2.95 adds code to the entry and exit point of every function to align the
|
|
|
|
# stack to 16-byte boundaries -- thus wasting approximately 12 bytes of stack
|
|
|
|
# per function call. While the 16-byte alignment may benefit micro benchmarks,
|
|
|
|
# it is probably an overall loose as it makes the code bigger (less efficient
|
|
|
|
# use of code cache tag lines) and uses more stack (less efficient use of data
|
|
|
|
# cache tag lines)
|
|
|
|
#
|
|
|
|
.if ${MACHINE_ARCH} == "i386"
|
|
|
|
CFLAGS+= -mpreferred-stack-boundary=2
|
|
|
|
.endif
|
|
|
|
|
1998-12-17 22:36:21 +00:00
|
|
|
#
|
|
|
|
# On the alpha, make sure that we don't use floating-point registers and
|
|
|
|
# allow the use of EV56 instructions (only needed for low-level i/o).
|
|
|
|
#
|
|
|
|
.if ${MACHINE_ARCH} == "alpha"
|
|
|
|
CFLAGS+= -mno-fp-regs -Wa,-mev56
|
|
|
|
.endif
|