From: lauras AT softhome DOT net
Message-ID: <20010707153645.23586.qmail@softhome.net>
To: djgpp-workers AT delorie DOT com
Cc: eliz AT is DOT elta DOT co DOT il
Subject: Re: Comments on GCC 3.0 distribution 
Date: Sat, 07 Jul 2001 15:36:45 GMT
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: lauras AT softhome DOT net
Reply-To: djgpp-workers AT delorie DOT com



> I see that lib/gcc-lib/djgpp/3.0/include has several header files,
> such as limits.h, stdarg.h, stddef.h.  Not all of them have
> #include_next, so I'm wondering whether GCC uses those headers in
> preference to ours, and if so, what ckind of trouble can that do.  For
> example, our stddef.h includes sys/djtypes.h, but the one which comes
> with GCC does not.
> 
> Even if they all had #include_next, I'm not sure GCC will pick up our
> files.  Did someone verify that?
>
> I admit that I don't remember what was the agreement back when we
> discussed this issue.

Oh... This one. My asbestos underwear still has old stains from that
discussion with GCC team. Lucky for us, the situation isn't that bad -
those headers rely on preprocessor symbols to get actual type definitions
and stuff. And those symbols are defined by target configuration file in
GCC, in other words, by us. Mark has done it, and now GCC and our
headers fully agree about type sizes etc. Things could be much worse,
as I remember those flame wars.

Laurynas