From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1InDnG-0003fq-JP for qemu-devel@nongnu.org; Wed, 31 Oct 2007 09:39:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1InDnE-0003bg-8z for qemu-devel@nongnu.org; Wed, 31 Oct 2007 09:39:37 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1InDnD-0003bA-Tq for qemu-devel@nongnu.org; Wed, 31 Oct 2007 09:39:36 -0400 Received: from [66.135.41.201] (helo=server2linux.rebelnetworks.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1InDnD-0002aG-D5 for qemu-devel@nongnu.org; Wed, 31 Oct 2007 09:39:35 -0400 From: Julian Seward Date: Wed, 31 Oct 2007 14:39:04 +0100 References: <200710311237.22174.jseward@acm.org> <1193837243.24629.22.camel@jma4.dev.netgem.com> In-Reply-To: <1193837243.24629.22.camel@jma4.dev.netgem.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710311439.04939.jseward@acm.org> Subject: [Qemu-devel] Re: emu errors for creqv,crnand,crnor,crorc ? Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: l_indien@magic.fr Cc: qemu-devel@nongnu.org > > way around. Below is a simple test case. On QEMU it prints > > > > result is 000fc000 > > > > and on a real 7447 > > > > result is 00004000 > > > What is strange is that 0xFC + 0x04... I will have to check all the CR > ops, I guess... Another strange thing is that 000fc000 does not have 'fc' byte-aligned inside CR, if you see what I mean. If it was 0000fc00 or 00fc0000, some byte-inversion mistake would seem likely. This isn't a 74xx specific result. I'm sure any ppc should produce 00004000. The test is very simple: make CR=0 then do crorc 17,14,15. So only 1 bit in CR will then be set - all others are zero. J