Re: GCC 4.1.1 RC1 -- third bootstrap error alpha-dec-osf4.0

["Marc W. Mengel" <mengel at fnal dot gov>]

This is probably very low priority, maybe a release note?

In the dim-and-musty-systems department, using

Compaq C V6.1-120 on Digital UNIX V4.0G (Rev. 1530)

We get:
cc -c -DHAVE_CONFIG_H -g  -I. 
-I/tmp/build-gcc-v4_1_1/src/gcc-4.1.1-20060517/libiberty/../include 
/tmp/build-gcc-v4_1_1/src/gcc-4.1.1-20060517/libiberty/hashtab.c -o 
hashtab.o
cc: Error: 
/tmp/build-gcc-v4_1_1/src/gcc-4.1.1-20060517/libiberty/hashtab.c, line 
197: In this declaration, parameter 1 has a different type than 
specified in an earlier declaration of this function. (mismatparam)
hash_pointer (const PTR p)
^
cc: Error: 
/tmp/build-gcc-v4_1_1/src/gcc-4.1.1-20060517/libiberty/hashtab.c, line 
197: In this declaration, the type of "hash_pointer" is not compatible 
with the type of a previous declaration of "hash_pointer" at line number 
71 in file 
/tmp/build-gcc-v4_1_1/src/gcc-4.1.1-20060517/libiberty/hashtab.c. 
(notcompat)
hash_pointer (const PTR p)
^
cc: Error: 
/tmp/build-gcc-v4_1_1/src/gcc-4.1.1-20060517/libiberty/hashtab.c, line 
205: In this declaration, parameter 1 has a different type than 
specified in an earlier declaration of this function. (mismatparam)
eq_pointer (const PTR p1, const PTR p2)
^
....

It goes on like this for quite a while.  LOTS of inconsisencies of using 
PTR one place and void * in another...

Marc Mengel <mengel@fnal.gov>