Warnings while compiling glibc-2.3.1 for cris

[Uwe Reimann]

Hi,

during cross compiling glibc-2.3.1 for cris with gcc-2.3.2 I get the 
following warnings (extracted with "fgrep -i warning compile_glibc.out 
| sort -u"):

../linuxthreads/sysdeps/cris/pspinlock.c:31: warning: passing arg 1 of 
`testandset' discards qualifiers from pointer target type
../linuxthreads/sysdeps/cris/pspinlock.c:42: warning: passing arg 1 of 
`testandset' discards qualifiers from pointer target type
../math/bits/cmathcalls.h:117: warning: conflicting types for built-in 
function `conjl'
../math/bits/cmathcalls.h:126: warning: conflicting types for built-in 
function `cimagl'
../math/bits/cmathcalls.h:129: warning: conflicting types for built-in 
function `creall'
../sysdeps/cris/memcopy.h:30:1: warning: "WORD_COPY_FWD" redefined
../sysdeps/cris/memcopy.h:44:1: warning: "WORD_COPY_BWD" redefined
../sysdeps/generic/atomicity.h:25:2: warning: #warning stub atomicity 
functions are not atomic
../sysdeps/generic/memcopy.h:116:1: warning: this is the location of the 
previous definition
../sysdeps/generic/memcopy.h:136:1: warning: this is the location of the 
previous definition
../sysdeps/generic/setfpucw.c:29: warning: statement with no effect
../sysdeps/generic/w_sqrt.c:46: warning: conflicting types for built-in 
function `sqrtl'
../sysdeps/ieee754/dbl-64/s_fabs.c:39: warning: conflicting types for 
built-in function `fabsl'
../sysdeps/ieee754/dbl-64/s_sin.c:1126: warning: conflicting types for 
built-in function `sinl'
../sysdeps/ieee754/dbl-64/s_sin.c:1128: warning: conflicting types for 
built-in function `cosl'
fileops.c:1551: warning: weak declaration of `_IO_do_write' after first 
use results in unspecified behavior
programs/ld-monetary.c:282: warning: comparison is always false due to 
limited range of data type
programs/ld-monetary.c:283: warning: comparison is always false due to 
limited range of data type
regexec.c:1783: warning: `node' might be used uninitialized in this function

Does any of those indicate that something serious is wrong?

Best regards, Uwe