This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: [geoffk@cygnus.com: GCC testing failed with your patch.]
- To: Geoff Keating <geoffk at cygnus dot com>
- Subject: Re: [geoffk@cygnus.com: GCC testing failed with your patch.]
- From: Alan Modra <alan at linuxcare dot com dot au>
- Date: Sat, 25 Mar 2000 20:33:41 +1100 (EST)
- cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, gcc-bugs at gcc dot gnu dot org
On Fri, 24 Mar 2000, Geoff Keating wrote:
> /thief/plunder/objs/H-i686-pc-linux-gnu/powerpc-eabisim/include/string.h:55: war
> ning: new declaration `int bcmp (const char *, const char *, unsigned int)'
> /thief/plunder/objs/H-i686-pc-linux-gnu/powerpc-eabisim/include/string.h:55: war
> ning: ambiguates built-in declaration `int bcmp (const void *, const void *, uns
> igned int)'
>
> I think you didn't mean 'void *'.
Just to add fuel to the fire, I'm quite happy with `void *', just don't
like `unsigned int' ;-)
On i586-linuxlibc1, I get libio and libstdc++ testsuite failures due to
this too. They are just warnings, but that bombs the test, which gets all
upset over any compiler output.
/usr/include/string.h:155: warning: new declaration `void bzero (void
/usr/include/string.h:155: warning: *, int)'
/usr/include/string.h:155: warning: ambiguates built-in declaration
/usr/include/string.h:155: warning: `void bzero (void *, unsigned int)'
/usr/include/string.h:158: warning: new declaration `int bcmp (const
/usr/include/string.h:158: warning: void *, const void *, int)'
/usr/include/string.h:158: warning: ambiguates built-in declaration
/usr/include/string.h:158: warning: `int bcmp (const void *, const void
/usr/include/string.h:158: warning: *, unsigned int)'
--
Linuxcare. Support for the Revolution.