From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Iy97d-0004IE-5w for qemu-devel@nongnu.org; Fri, 30 Nov 2007 11:53:49 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Iy97Z-0004Gt-MG for qemu-devel@nongnu.org; Fri, 30 Nov 2007 11:53:46 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iy97Z-0004Gn-AV for qemu-devel@nongnu.org; Fri, 30 Nov 2007 11:53:45 -0500 Received: from tapir.sajinet.com.pe ([66.139.79.212]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Iy97Z-0004nm-67 for qemu-devel@nongnu.org; Fri, 30 Nov 2007 11:53:45 -0500 Date: Fri, 30 Nov 2007 11:00:02 -0600 From: Carlo Marcelo Arenas Belon Subject: Re: [Qemu-devel] [PATCH] sh4: define explicitly that the target CPU is 32 bit Message-ID: <20071130170002.GG28369@tapir> References: <20071130162329.GF28369@tapir> <200711301628.09857.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200711301628.09857.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: Paul Brook Cc: qemu-devel@nongnu.org On Fri, Nov 30, 2007 at 04:28:09PM +0000, Paul Brook wrote: > On Friday 30 November 2007, Carlo Marcelo Arenas Belon wrote: > > The following patch enforces that the sh4 target is 32 bit to prevent qemu > > to expand incorrectly to a 64 bit wide cpu if compiled in a 64 bit host. > > This is wrong. As the comment in cpu-defs.h says, target_phys_addr_t may need > to be bigger than the actual target address space. > > What exactly are you trying to fix? in a generic way, that the CPU width of the host (as defined by the size of the type that is used to store a target_phys_addr_t) that is used to build the emulator affects in any way the size of the emulated target physical address size or its representation. in the sh4 specific case, it doesn't make sense for sh4 to print an access error to a physical address that is 64 bit long when it is a 32 bit CPU and that is what would happen unless the patch is applied. if anything the following definition from cpu-defs.h is invalid for a representation of a 32 bit physical address : #define TARGET_FMT_plx "%016" PRIx64 Carlo