From owner-freebsd-arm@FreeBSD.ORG Wed Oct 4 21:27:28 2006 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77DFD16A412; Wed, 4 Oct 2006 21:27:28 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79B9843D4C; Wed, 4 Oct 2006 21:27:23 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 2D68A140EC01; Wed, 4 Oct 2006 21:27:20 +0000 (GMT) Date: Wed, 4 Oct 2006 21:27:20 +0000 From: John Birrell To: Joseph Koshy Message-ID: <20061004212719.GA82760@what-creek.com> References: <20061004035533.GA76969@what-creek.com> <84dead720610040844o5dc873bt7185e164b20d699@mail.gmail.com> <20061004202004.GC82080@what-creek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061004202004.GC82080@what-creek.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-arm@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: Proposed elf header changes which affect PPC and ARM X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2006 21:27:28 -0000 On Wed, Oct 04, 2006 at 08:20:04PM +0000, John Birrell wrote: > On Wed, Oct 04, 2006 at 09:14:26PM +0530, Joseph Koshy wrote: > > >The patch: moves > > >all the relocation definitions for each arch from the machine/elf.h > > >header to sys/elf_common.h. > > > > What's the semantic difference between an 'Lword' and an 'Xword'? > > > > + typedef uint64_t Elf32_Lword; > > > > and... > > > > typedef int32_t Elf64_Sword; > > typedef int64_t Elf64_Sxword; > > typedef uint32_t Elf64_Word; > > + typedef uint64_t Elf64_Lword; > > typedef uint64_t Elf64_Xword; > > I'm not sure there is any. It's just something that OpenSolaris code > expects. I looked a bit further at this and I think that Lword probably changes it's size on OpenSolaris to be 32 bits if the code is being compiled in 32 bit mode whereas Xword is always 64 bits. -- John Birrell