[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200904021506.13942.arnd@arndb.de>
Date: Thu, 2 Apr 2009 15:06:12 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Roland McGrath <roland@...hat.com>
Cc: "H. Peter Anvin" <hpa@...or.com>,
Will Newton <will.newton@...il.com>,
Geert Uytterhoeven <geert.uytterhoeven@...il.com>,
michal.simek@...alogix.com,
Linux Kernel list <linux-kernel@...r.kernel.org>,
linux-arch@...r.kernel.org, linux-api@...r.kernel.org,
Chen Liqin <liqin.chen@...plusct.com>
Subject: Re: [RFC] asm-generic/{unistd,types,posix_types}.h for new arch
On Wednesday 01 April 2009, Roland McGrath wrote:
> > Actually, gcc does have the _LP64 and __SIZEOF_POINTER__ macros (as well
> > as __CHAR_BIT__), although I don't know how far back it does have that.
> > If it has been with us for long enough it might be possible to
> > switch over to using panarch macros.
For user space, we also need to consider non-gcc compilers that could have
a different set of macros. As long as we don't start relying on any new
ones besides those we already use (__x86_64__, __s390x__, __powerpc64__,
__mips64, __arch64__), we at least don't break anything accidentally.
> Worst case the oldest compilers had <limits.h> and
> "#if ULONG_MAX == 0xffffffffUL", though I wouldn't like
> myself to be using a setup where <limits.h> got pulled in.
That would of course work with non-gcc, but we are really not allowed
to pull in <limits.h> from places like <types.h> where it would be needed
then.
Arnd <><
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists