This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: moving <limits> bits to config/cpu
- To: Phil Edwards <pedwards at disaster dot jaj dot com>, Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- Subject: Re: moving <limits> bits to config/cpu
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Thu, 23 Aug 2001 21:49:19 -0700
- cc: "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>, "bkoz at redhat dot com" <bkoz at redhat dot com>
> The (admittedly baroque) way that gcc handles its config files might help
> us here. If configure.* sets LIMITSH to not a single file but rather
> a list of files which are then concatenated to form limits.h, then the
> OS/limits.h can override the CPU/limits.h.
FWIW, what I think makes sense is that you put the "usual" definitions
for an architecture in cpu/limits.h. Then, if that's not right for
your OS, you turn off the use of cpu/limits.h in the configury stuff,
and put the stuff you need in yours os_defines.h, or os/limits.h,
or whatever.
My two cents,
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com