From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [RFC] asm-generic/{unistd,types,posix_types}.h for new arch Date: Thu, 2 Apr 2009 15:06:12 +0200 Message-ID: <200904021506.13942.arnd@arndb.de> References: <49D071A8.4010703@petalogix.com> <49D3DABA.2050001@zytor.com> <20090401213219.7B324FC3AB@magilla.sf.frob.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20090401213219.7B324FC3AB-nL1rrgvulkc2UH6IwYuUx0EOCMrvLtNR@public.gmane.org> Content-Disposition: inline Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Roland McGrath Cc: "H. Peter Anvin" , Will Newton , Geert Uytterhoeven , michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org, Linux Kernel list , linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Chen Liqin List-Id: linux-arch.vger.kernel.org On Wednesday 01 April 2009, Roland McGrath wrote: > > Actually, gcc does have the _LP64 and __SIZEOF_POINTER__ macros (as= well=20 > > as __CHAR_BIT__), although I don't know how far back it does have t= hat.=20 > > =A0 =A0 =A0If it has been with us for long enough it might be possi= ble to=20 > > switch over to using panarch macros. =46or 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 and=20 > "#if ULONG_MAX =3D=3D 0xffffffffUL", though I wouldn't like > myself to be using a setup where got pulled in. That would of course work with non-gcc, but we are really not allowed to pull in from places like where it would be need= ed then. Arnd <>< -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de ([212.227.126.177]:57760 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750843AbZDBNG1 convert rfc822-to-8bit (ORCPT ); Thu, 2 Apr 2009 09:06:27 -0400 From: Arnd Bergmann Subject: Re: [RFC] asm-generic/{unistd,types,posix_types}.h for new arch Date: Thu, 2 Apr 2009 15:06:12 +0200 References: <49D071A8.4010703@petalogix.com> <49D3DABA.2050001@zytor.com> <20090401213219.7B324FC3AB@magilla.sf.frob.com> In-Reply-To: <20090401213219.7B324FC3AB@magilla.sf.frob.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-ID: <200904021506.13942.arnd@arndb.de> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Roland McGrath Cc: "H. Peter Anvin" , Will Newton , Geert Uytterhoeven , michal.simek@petalogix.com, Linux Kernel list , linux-arch@vger.kernel.org, linux-api@vger.kernel.org, Chen Liqin Message-ID: <20090402130612.1fOxjH9z4U5OJ68iIN_9IOC_LuZqQYMWyNEUFxB9QMw@z> 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 and > "#if ULONG_MAX == 0xffffffffUL", though I wouldn't like > myself to be using a setup where got pulled in. That would of course work with non-gcc, but we are really not allowed to pull in from places like where it would be needed then. Arnd <><