From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joel Sherrill <joel@OARcorp.com>
To: Christian Iseli <chris@lslsun.epfl.ch>
Cc: egcs@cygnus.com
Subject: Re: xlimits.h for embedded targets
Date: Tue, 14 Oct 1997 04:57:00 -0000
Message-id: <Pine.BSF.3.96.971014065332.23902A-100000@vespucci.advicom.net>
References: <199710140628.IAA20692@lslsun17.epfl.ch>
X-SW-Source: 1997-10/msg00532.html

On Tue, 14 Oct 1997, Christian Iseli wrote:

> > Then maybe newlib should be "fixing" gcc's limits.h rather than the other
> > way around.
> 
> I'll second that.  Some targets will probably not use newlib...
> 
> Seems to me that maybe the cleanest way would be to generate a basic
> limits.h from the target description file (tm.h).  That's GCC's idea
> of the target's limits anyway.  At first glance, this should not be
> too hard... (famous last words, I know ;-)
> 
> What do you think?

I need to look into this further but it should not be too terribly bad to
have the newlib installed limits.h include the one gcc generates when it
does not see a limits.h.  At that point, it should just be a matter of
getting the include path search order right.  

--joel