Carlos Henrique Bauer (firstname.lastname@example.org)
Wed, 17 Mar 1999 20:28:50 -0300
On Tue, 16 Mar 1999, Tim Waugh wrote:
>It is though, and in clean 2.2.3. What does 'nm parport.o | grep memset'
>say, and which compiler are you using? It sounds like the kind of thing
>that would break if you forgot to use optimisation.
Here is the info from nm:
I'm using gcc 188.8.131.52. It must be a compiler bug. I compiled the file
parport_share.c with the command:
gcc -E -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 \
-fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 \
-malign-jumps=2 -malign-functions=2 -DCPU=686 -DMODULE -DMODVERSIONS -include \
/usr/src/linux/include/linux/modversions.h -c -o parport_share.out \
That writes the output of the preprocessor the file parport_share.out. There
is just one line in the output where memset appears:
extern void * memset(void *,int,__kernel_size_t);
The line comes from the file /usr/src/linux/include/string.h.
Should I move to another compiler?
Carlos Henrique Bauer
-- To unsubscribe, send mail to: email@example.com -- -- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Sun 28 Mar 1999 - 17:01:38 EST