From owner-freebsd-current@FreeBSD.ORG Fri Sep 7 12:05:42 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9855916A41B for ; Fri, 7 Sep 2007 12:05:42 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id 70D5413C45E for ; Fri, 7 Sep 2007 12:05:42 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l87C3AM6094682; Fri, 7 Sep 2007 05:03:10 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l87C3Ac6094681; Fri, 7 Sep 2007 05:03:10 -0700 (PDT) (envelope-from rizzo) Date: Fri, 7 Sep 2007 05:03:10 -0700 From: Luigi Rizzo To: Giorgos Keramidas Message-ID: <20070907050310.A94579@xorpc.icir.org> References: <20070906111028.A83649@xorpc.icir.org> <20070906222647.GB2737@kobe.laptop> <20070907000950.A91211@xorpc.icir.org> <20070907115021.GA2718@kobe.laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20070907115021.GA2718@kobe.laptop>; from keramida@ceid.upatras.gr on Fri, Sep 07, 2007 at 02:50:21PM +0300 Cc: current@freebsd.org Subject: Re: how to tell 64 vs 32 bit architecture ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Sep 2007 12:05:42 -0000 On Fri, Sep 07, 2007 at 02:50:21PM +0300, Giorgos Keramidas wrote: > On 2007-09-07 00:09, Luigi Rizzo wrote: > >On Fri, Sep 07, 2007 at 01:26:47AM +0300, Giorgos Keramidas wrote: > >>On 2007-09-06 11:10, Luigi Rizzo wrote: > >>> hi, > >>> i was wondering what is the proper way to tell a 64 vs 32 bit > >>> architecture. > >>> > >>> I see that some code in sys/ uses ' #ifdef __LP64__ ' but i am not > >>> sure if this is generic enough (ie not gcc or FreeBSD specific), > >>> and also suitable for userland (i.e. works on linux or other platforms > >>> as well). > >> > >> This is usually needed to differentiate between a feature "X" which > >> behaves differently in amd64 vs. i386 vs. sparc vs. sparc64, etc. > > > > i am actually looking at pointer sizes, as i need to do some pointer > > manipulation going through intptr_t, and need to know that in the > > preprocessor because some constants need to be 32 or 64 bit depending > > on that, and are not trivial (i.e. not 0, 1 or something i can build > > with size-agnostic expressions) > > An intptr_t can safely hold any void pointer value, and C99 says: > > % 7.18.1.4 Integer types capable of holding object pointers > % > % 1 The following type designates a signed integer type with the > % property that any valid pointer to void can be converted to > % this type, then converted back to pointer to void, and the > % result will compare equal to the original pointer: > % > % intptr_t > > What sort of manipulation? Can this sort of manipulation be written in > a way that uses sizeof(intptr_t) instead of 4, 8, or preprocessor magic? i need to do this: #ifdef BUILT_FOR_64BIT_POINTERS #define MY_MAGIC 0xdeadbeefd00de123 /* 64 bit */ #else #define MY_MAGIC 0xdeadbeef /* 32 bit */ If you know of a way to implement this without preprocessor magic, i am all ears. If the values were simpler (eg all ones or so) i could have used ~((unitptr_t)0) but this is not the case here cheers luigi