From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HD758-00073x-HN for qemu-devel@nongnu.org; Fri, 02 Feb 2007 17:40:34 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HD756-000737-Ru for qemu-devel@nongnu.org; Fri, 02 Feb 2007 17:40:34 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HD756-000731-OM for qemu-devel@nongnu.org; Fri, 02 Feb 2007 17:40:32 -0500 Received: from mail.codesourcery.com ([65.74.133.4]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HD756-0007zb-0d for qemu-devel@nongnu.org; Fri, 02 Feb 2007 17:40:32 -0500 From: Paul Brook Subject: Re: [Qemu-devel] Re: strange crash on FreeBSD-current/amd64 (pointer truncation?) Date: Fri, 2 Feb 2007 22:40:21 +0000 References: <20070124200019.GA36641@saturn.kn-bremen.de> <20070202214525.GA10125@saturn.kn-bremen.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702022240.22482.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, balrogg@gmail.com > > Isn't that 32 bit for 32 bit targets? Then it wouldn't fix the bug, > > Well, it just happens that target_ulong is 64 bit even for 32 bit > target on a 64 bit host (as a workaround for something I think, was > wondering about it too. I asked on IRC once but no one knew the actual > reason). This however doesn't change the fact that target_ulong > shouldn't be used here. Are you sure you're not confusing it with target_phys_address_t? Paul