GCC Steering Committee decision on ISO C conversion

[John David Anglin]

>  > From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
>  > 
>  > See PR 7170.  The main problem is the string concatenation used in the
>  > definition of re_error_msgid.  If you have thoughts on a good way to
>  > fix this let me know.
> 
> I know the problem, in fact gcc-3.x -Wtraditional warns about it when
> compiling regex.c.  But I don't have any suggestions on how to fix it
> that are clean and/or minimally invasive.
> 
> However AFAICT, we don't actually use libibety's regex.o anywhere in
> gcc so maybe you can just not compile it if configure determines that
> your stage1 compiler is lame. (?)

What about the other packages that use libiberty (eg., binutils)?  If
gcc will build the C language using the native tools, then the above
could be a viable bootstrap approach.

I guess what could be done is to initialize re_error_msgid at runtime
in a manner similar to re_syntax_table if the stage1 compiler doesn't
support string concatenation.

> Regarding 7163, this doesn't occur for me either and the warning
> message doesn't say where the second half of the conflict occurred.
> You need to provide preprocessed source for me to be able to offer any
> assistance.

I will try to go through these in detail after the holiday and provide
patches.  

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)