PostgreSQL 8.2 : warnings during the built with ICC 9.1.045

Hello List,

I try to post this e-mail on this list, as nobody answers me on 
pgsql-general :-(
I work with an IA-64 server with Red Hat Enterprise Linux 4 AS update 2 
on which the Intel compiler icc 9.1.045 is available and I build 
PostgreSQL 8.2 with this compiler.
To do that I generated RPM from the "postgresql-8.2.0-2PGDG.src.rpm" 
with the command "rpmbuild -ba postgresql-8.2.spec"

I noticed a lot of warnings in the log of the "rpmbuild -ba" command.
I put below some of these warnings :
parse_expr.c(2066): warning #188: enumerated type mixed with another type                      rctype = 0;
      /* keep compiler 
 
quiet */

../../../../src/include/storage/s_lock.h(246): warning #167: argument of 
type "volatile slock_t={unsigned int} *" is incompatible with parameter 
of type "void *"      ret = _InterlockedExchange(lock,1);     /* this is a xchg asm 
macro */

hba.c(1476): warning #167: argument of type "int *" is incompatible with 
parameter of type "socklen_t={__socklen_t={unsigned int}} *restrict"      if (getsockopt(sock, SOL_SOCKET, SO_PEERCRED,
&peercred,&so_len) 
 
!= 0 ||

regc_locale.c(358): warning #186: pointless comparison of unsigned 
integer with zero      return (c >= 0 && c <= UCHAR_MAX && isdigit((unsigned char) c));

dfmgr.c(117): warning #556: a value of type "void *" cannot be assigned 
to an entity of type "PGFunction"      retval = pg_dlsym(lib_handle, funcname);             ^
dfmgr.c(165): warning #120: return value type does not match the 
function type      return pg_dlsym(filehandle, funcname);

fe-misc.c(167): warning #186: pointless comparison of unsigned integer 
with zero      if (len < 0 || len > (size_t) (conn->inEnd - conn->inCursor))

mbuf.c(45): warning #108: implicitly-signed bit field of length 1      int                     no_write:1;

These numbers of warning (#188, #167, #186, #556, #120, #186, #108) 
represent all the warrnings contained in the log file.

Could someone tell me if these warnings can have a negative impact on 
the performances of PostgreSQL ?

Thank you in advance.
Regards,
Alexandra DANTE