From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36851) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YTw0U-0001b6-OV for qemu-devel@nongnu.org; Fri, 06 Mar 2015 12:25:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YTw0P-0005Xu-6o for qemu-devel@nongnu.org; Fri, 06 Mar 2015 12:25:50 -0500 Received: (from localhost user: 'macro', uid#1010) by eddie.linux-mips.org with ESMTP id S27012707AbbCFRZnZB1YT (ORCPT + 1 other); Fri, 6 Mar 2015 18:25:43 +0100 Date: Fri, 6 Mar 2015 17:25:43 +0000 (GMT) Sender: "Maciej W. Rozycki" From: "Maciej W. Rozycki" In-Reply-To: <71EF659E-A1A2-4938-A99B-856168D156B6@suse.de> Message-ID: References: <54F9CFF5.4070800@suse.de> <71EF659E-A1A2-4938-A99B-856168D156B6@suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [Qemu-devel] mfocrf missing on e500v2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-ppc , qemu-devel , Richard Henderson On Fri, 6 Mar 2015, Alexander Graf wrote: > >> And lo and behold, I really couldn't find any reference to mfocrf in the > >> e500v2 spec. > > > > Do real e500 processors trap on this operation as well? > > The illegal instruction I posted about above was when running qemu > *on* e500v2, because TCG emits mfocrf ;). Ah OK, fair enough! I guess that answers the question. Maciej