PATCH: Check LONG_MAX > INT_MAX for __WORDSIZE
Paul Eggert
eggert@cs.ucla.edu
Fri Apr 13 02:57:00 GMT 2012
On 04/12/2012 05:31 PM, H.J. Lu wrote:
> This path includes <limits.h> and checks LONG_MAX > INT_MAX for this case.
There a namespace pollution problem here, unfortunately. For example,
because stdint.h includes bits/wordsize.h and the proposed change
would cause bits/wordsize.h to sometimes include limits.h, the
proposed change would cause <stdint.h> to sometimes #define MAX_CANON,
which is not at all what we want.
Also, I don't see how it works in general, since this would have
bits/wordsize.h include limits.h which includes bits/wordsize.h again,
and the whole thing is looking pretty incestuous, at least on some
platforms.
More information about the Libc-alpha
mailing list