rwsem, gcc3 again
David,
I am using the gcc-3.0 snapshot of 14.5.2001 from codesourcery (i686 binary). I have now tried to mimic CPU=386 behaviour (patch posted yesterday night) and it compiles (just sound fails), by exchanging y and n in CONFIG_RWSEM_GENERIC_SPINLOCK and CONFIG_RWSEM_XCHGADD_ALGORITHM.
Thanks for your patience, all listening...
-mirabilos
Signature · 1 line
by telnet
Quoted 7 lines · On Wed, May 16, 2001 at 11:03:27AM +0200, [email protected] wrote:
David,
I am using the gcc-3.0 snapshot of 14.5.2001 from codesourcery (i686 binary). I have now tried to mimic CPU=386 behaviour (patch posted yesterday night) and it compiles (just sound fails), by exchanging y and n inCONFIG_RWSEM_GENERIC_SPINLOCKandCONFIG_RWSEM_XCHGADD_ALGORITHM.Thanks for your patience, all listening...
can you check if the alternate rwsem compiles with gcc 3.0? I had a report that they don't compile but I checked and that had to be a gcc 3.0 bug, and so I was waiting to hear they start to compile with latest CVS of gcc 3.0.
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.5pre2aa1/00_rwsem-11
Andrea
Hi Andrea:
Here you go:
/usr/local/bin/gcc -D__KERNEL__ -I/inst-kernels/linux-2.4.5-pre2-aa/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i686 -DEXPORT_SYMTAB -c sys.csys.c: In function `sys_gethostname':
/inst-kernels/linux-2.4.5-pre2-aa/include/asm/rwsem_xchgadd.h:51: inconsistent operand constraints in an `asm'
I've lit fires underneath some of our gcc people, and they say it's definitely a bug in gcc. They're currently looking at it.
David
Quoted 5 lines · David Howells
Hi Andrea:
Here you go:
Quoted 7 lines
/usr/local/bin/gcc-D__KERNEL__ -I/inst-kernels/linux-2.4.5-pre2-aa/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i686 -DEXPORT_SYMTAB -csys.csys.c: In function `sys_gethostname':
/inst-kernels/linux-2.4.5-pre2-aa/include/asm/rwsem_xchgadd.h:51: inconsistent operand constraints in an `asm'I've lit fires underneath some of our gcc people, and they say it's definitely a bug in gcc. They're currently looking at it.
Ok, I hope it will be fixed soon ;), thanks for checking.
Andrea