src.conf: CFLAGS/COPTFLAGS inconsistency

[O. Hartmann]

man make.conf states, that COPTFLAGS is used for building/compiling the kernel
(exclusively). The question arises: are kernel modules NOT kernel or are they kernel?

The problem I face is that with optimization level -O3 loader.efi gets miscompiled and a
UEFI laptop stops/reject booting. To avoid other interference, I defined COPTFLAGS
in /etc/src.conf accordingly, but leave CFLAGS?=-O3 in /etc/make.conf for compilation of
regular ports and the rest of the OS.

I can observe that with CFLAGS set, either in make.conf, or src.conf or mutual exclusive,
the CFLAGS is ALWAYS incorporated when kernel stuff like modules and even the loader.efi
is built! I consider this inconsitent, since loader.efi is definitely kernel related
stuff as well as modules.

It seems to me that it s not possible to separate cleanly CFLAGS and COPTFLAGS for
userland/ports and kernel-only related compilations as described in the man page. 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20140919/b6624e12/attachment.sig>