In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes:
>
># make
>cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -Wall -Wredundant-decls -Wnested-externs
>-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
>-fformat-extensions -ansi -g -nostdinc -I- -I. -I../../.. -I../../../dev
>-I../../../contrib/dev/acpica -I../../../contrib/ipfilter -D_KERNEL
> -include opt_global.h -fno-common -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding
>-Werror ../../../alpha/alpha/interrupt.c
>cc1: warnings being treated as errors
>../../../alpha/alpha/interrupt.c: In function `alpha_clock_interrupt':
>../../../alpha/alpha/interrupt.c:483: warning: passing arg 1 of `statclock_process'
>from incompatible pointer type
>*** Error code 1
Sorry for replying to myself, but it seems to me that the
KSE-intelligensia needs to test on more than i386-UP.
Considering that we can cross-build kernels, I think there is no valid
excuse for such blatant: "it works for me!" testing:
bang# sh gsys statclock_process
./alpha/alpha/interrupt.c: statclock_process(curkse,
TRAPF_PC(framep),
./i386/i386/critical.c: statclock_process(curthread,
./i386/i386/mp_machdep.c: * WARNING! unpend() will call statclock_process() directly
and skip this
./i386/i386/mp_machdep.c: statclock_process(curthread->td_kse, TRAPF_PC(&frame),
./ia64/ia64/interrupt.c:statclock_process(curkse,
TRAPF_PC(framep),
./kern/kern_clock.c:statclock_process(struct thread *td, register_t pc, int user)
./kern/kern_clock.c:statclock_process(curthread, CLKF_PC(frame),
CLKF_USERMODE(frame));
./sparc64/sparc64/tick.c: statclock_process(curthread->td_kse,
CLKF_PC(cf),
./sys/systm.h:void statclock_process(struct thread *td, register_t pc, int user);
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
