Re: moving <limits> bits to config/cpu

[Phil Edwards <pedwards at disaster dot jaj dot com>]

On Thu, Aug 23, 2001 at 02:10:59PM -0500, Loren James Rittle wrote:
> In article <Pine.SOL.3.91.1010823114350.748B-100000@taarna.cygnus.com>:
> > I think this approach to <limits> makes the most sense. At the risk of 
> > opening another can of worms, would it be possible to convert all the 
> > current limits bits to use this (sane) approach, instead of the current 
> > hodge podge approach? Or am I missing something?
> 
> >>         * configure.target: Set LIMITSH for powerpc-*-*.
> >>         * config/cpu/powerpc/bits/limits.h: New file.
> 
> My only concern is that not every OS on the same CPU has the same
> limits properties...
> 
> I just hit this with FreeBSD/i386 not being the same as Linux/i386.

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.


Phil

-- 
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
                                     - anonymous Egyptian scribe, c.1700 BC