From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Alexander Stein Date: Wed, 01 Feb 2012 13:49:22 +0100 Message-ID: <10381918.aAGBVVShah@ws-stein> In-Reply-To: <20120131141208.GA32382@pengutronix.de> References: <2236550.JcqvJ5vtdt@ws-stein> <1449371.MGWo599kFb@ws-stein> <20120131141208.GA32382@pengutronix.de> MIME-Version: 1.0 Subject: Re: [ptxdist] Detect if x86 target is 32 or 64bit? Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: Michael Olbrich On Tuesday 31 January 2012 15:12:08 Michael Olbrich wrote: > On Tue, Jan 31, 2012 at 09:21:30AM +0100, Alexander Stein wrote: > > On Wednesday 04 January 2012 17:59:57 Michael Olbrich wrote: > > > On Wed, Jan 04, 2012 at 03:27:46PM +0100, Alexander Stein wrote: > > > > how can I detect if a x86 target is 32 or 64bit? I'm working on a package > > rule > > > > for gnu-efi and elilo which need to know if it should generate ia32, > > x86_64 > > > > (or ia64) binaries. > > > > I just know about PTXCONF_ARCH_X86 but this does not show what I want. > > There > > > > is also PTXCONF_KERNEL_ARCH_X86_64 for 64bit but this needs a linux kernel > > > > configured. Any other ideas? > > > > > > This is not yet supported. You'll need to add ARCH_X86_64 and ARCH_IA64 to > > > platforms/architecture.in and set the correct defaults for HAS_HARDFLOAT > > > etc. > > > Send patches :-) > > > > I doubt it's the best way to just add ARCH_X86_64 (and maybe ARCH_IA64). A lot > > of rules files use "ifdef PTXCONF_ARCH_X86". So this has to be reworked to be > > useable in X86_64, as most cases don't make a difference to 32 or 64 Bit. > > Maybe it's better, to add a 64Bit entry in the optimization. Thoughts? > > I have no idea which way will be easier to implement. But I don't think > adding to the optimization is the best. There will be places where you need > to separate 32 vs 64 bit (e.g. SIZEOF_LONG_DOUBLE). > So I guess you should start with a (ARCH_X86_32|ARCH_X86_64) choice and > check if any "ifdef PTXCONF_ARCH_X86" need to be changed. > If there are few/no uses of ARCH_X86 left then we can rename ARCH_X86_32 to > ARCH_X86. Another problem prio to this is a 64bit toolchain in ptxdist. Up to now there is no OSELAStoolchain for x86_64. So I tried to use my host toolchain, but ptxdist cannot detect the sysroot in ptxd_init_sysroot_toolchain. At least my host toolchain has no --sysroot configure option set. I will assume an application is for 32bit, at the moment. Best regards, Alexander -- Dipl.-Inf. Alexander Stein SYS TEC electronic GmbH August-Bebel-Str. 29 D-07973 Greiz Tel: +49-3661-6279-0, Fax: +49-3661-6279-99 eMail: Alexander.Stein@systec-electronic.com Internet: http://www.systec-electronic.com Managing Director: Dipl.-Phys. Siegmar Schmidt Commercial registry: Amtsgericht Jena, HRB 205563 -- ptxdist mailing list ptxdist@pengutronix.de