Date: Thu, 20 Jul 2000 02:44:16 -0400 (EDT)
Message-Id: <200007200644.CAA09337@indy.delorie.com>
From: Eli Zaretskii <eliz AT delorie DOT com>
To: mrs AT windriver DOT com
CC: djgpp-workers AT delorie DOT com, gcc AT gcc DOT gnu DOT org,
        martin AT loewis DOT home DOT cs DOT tu-berlin DOT de
In-reply-to: <200007192144.OAA01294@kankakee.wrs.com> (message from Mike Stump
	on Wed, 19 Jul 2000 14:44:15 -0700 (PDT))
Subject: Re: GCC headers and DJGPP port
References:  <200007192144 DOT OAA01294 AT kankakee DOT wrs DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: Mike Stump <mrs AT windriver DOT com>
> Date: Wed, 19 Jul 2000 14:44:15 -0700 (PDT)
>
> > Could you tell what other headers do we need to consider?
> 
> I'd rather tell you how to find the compiler include directories
> (touch t.c && gcc -v t.c), and how to run ls (dir).

The question was about future GCC releases, for which I cannot simply
look in my include directories.  I didn't want to waste your time by
arguing about problems that were already resolved.  For example, I
understand that it was decided to remove limits.h from the list of
installed headers in future GCC releases.

> errno.h limits.h proto.h varargs.h assert.h exception math.h stdarg.h
> syslimits.h curses.h fixed new stdbool.h typeinfo cxxabi.h iso646.h
> new.h stddef.h

Are all of these relevant for C programs?  exception, fixed, new,
typeinfo, cxxabi.h, and new.h seem to be for C++.  (I don't care about
C++ headers, since DJGPP uses the GNU version of libstdc++, and so no
conflicts should be caused by using GCC's C++-related headers.)

Ideally, I'd like to get rid of all of the above-mentioned headers
except varargs.h and stdarg.h.  What would we (the DJGPP maintainers)
need to do to come as close as possible to that goal?

In any case, the following headers out of the above list seem
especially dangerous:

  - errno.h
  - limits.h
  - assert.h
  - math.h
  - stddef.h

These all include definitions and declarations that are intimately
related to the libc internals.

I don't know what does proto.h include, but if it only defines the P_
macro for portable prototype declarations, it won't hurt.

As for syslimits.h, we don't have this header, so it should not be a
problem, unless it is included by varargs.h, stdarg.h, or some other
header that will be installed by GCC.