From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26982 invoked by alias); 10 Dec 2002 21:41:40 -0000 Mailing-List: contact cgen-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sources.redhat.com Received: (qmail 26970 invoked from network); 10 Dec 2002 21:41:37 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 10 Dec 2002 21:41:37 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id gBALG3P31388 for ; Tue, 10 Dec 2002 16:16:03 -0500 Received: from hypatia.brisbane.redhat.com (IDENT:root@hypatia.brisbane.redhat.com [172.16.5.3]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id gBALfZD15002; Tue, 10 Dec 2002 16:41:35 -0500 Received: from walkabout.brisbane.redhat.com (kimba.brisbane.redhat.com [172.16.5.226]) by hypatia.brisbane.redhat.com (8.11.6/8.11.6) with ESMTP id gBALfY915148; Wed, 11 Dec 2002 07:41:34 +1000 Received: (from bje@localhost) by walkabout.brisbane.redhat.com (8.11.6/8.11.6) id gBALc7j18492; Wed, 11 Dec 2002 08:38:07 +1100 X-Authentication-Warning: walkabout.brisbane.redhat.com: bje set sender to bje@redhat.com using -f To: Doug Evans Cc: cgen@sources.redhat.com Subject: Re: bad shifts generated in sim code References: <200212100840.AAA12342@xris-athlon.transmeta.com> From: Ben Elliston Date: Tue, 10 Dec 2002 13:41:00 -0000 In-Reply-To: <200212100840.AAA12342@xris-athlon.transmeta.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-q4/txt/msg00065.txt.bz2 >>>>> "Doug" == Doug Evans writes: Doug> I found these in sim/m32r/decodex.c Doug> unsigned int val = (((insn >> -8) & (3 << 0))); Doug> unsigned int val = (((insn >> -12) & (1 << 0))); Doug> Someone want to fess up? I'm not sure there is any fessing to do. Has this file been regenerated lately? There was a bug in decoder generation that generated negative shifts which I thought we'd fixed. Ben