[src/trunk]: src/sys/conf sys/conf/lint.mk: allow GCC extensions in the kernel

[rillig <rillig%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/2c2fe36282fb
branches:  trunk
changeset: 983085:2c2fe36282fb
user:      rillig <rillig%NetBSD.org@localhost>
date:      Sun May 02 19:51:57 2021 +0000

description:
sys/conf/lint.mk: allow GCC extensions in the kernel

The syntax errors due to the __asm statements are now gone.  The file
kern_exec.c only produces a few warnings now.  But after running that
file through lint1, the main lint complains about wrong usage.  This is
due to this call:

        ${LINT} ... -i $< -o $@

The main lint has never supported -o after the first filename, so it
complains.  It would have been helpful if lint had given any hint as to
which option was invalid.  Anyway, the next step is to reorder the
arguments.  As it is now, the code can never have worked.

diffstat:

 sys/conf/lint.mk |  4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diffs (18 lines):

diff -r 2e01a3c17e1e -r 2c2fe36282fb sys/conf/lint.mk
--- a/sys/conf/lint.mk  Sun May 02 19:29:30 2021 +0000
+++ b/sys/conf/lint.mk  Sun May 02 19:51:57 2021 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: lint.mk,v 1.2 2021/05/02 19:29:30 rillig Exp $
+# $NetBSD: lint.mk,v 1.3 2021/05/02 19:51:57 rillig Exp $
 
 ##
 ## lint
@@ -8,7 +8,7 @@
 .PATH: $S
 ALLSFILES?=    ${MD_SFILES} ${SFILES}
 LINTSTUBS?=    ${ALLSFILES:T:R:C/^.*$/LintStub_&.c/g}
-KERNLINTFLAGS?=        -bcehnxzFS
+KERNLINTFLAGS?=        -bceghnxzFS
 NORMAL_LN?=    ${LINT} ${KERNLINTFLAGS} ${CPPFLAGS:M-[IDU]*} -i $< -o $@
 
 _lsrc=${CFILES} ${LINTSTUBS} ${MI_CFILES} ${MD_CFILES}