Garrett Wollman writes:
> > Somebody remind me again why we don't make memcmp(), memset(),
> > and memmove() available in the kernel?
>
> To keep the compiler from pessimizing them.
Sooo.. does this same problem exist in userland too? If not, why
not? If so, why don't we just fix the problem?
Poul-Henning Kamp writes:
> linking kernel
> umodem.o: In function `umodem_set_line_coding':
> umodem.o(.text+0xe6a): undefined reference to `memcmp'
Somebody remind me again why we don't make memcmp(), memset(),
and memmove() available in the kernel? Seems silly, especially
since we have things
< said:
> Somebody remind me again why we don't make memcmp(), memset(),
> and memmove() available in the kernel?
To keep the compiler from pessimizing them.
-GAWollman
--
Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED] | O Siem / The fires o
syv# make -k
linking kernel
umodem.o: In function `umodem_set_line_coding':
umodem.o(.text+0xe6a): undefined reference to `memcmp'
*** Error code 1 (continuing)
`all' not remade because of errors.
syv#
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP si
