From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31282 invoked by alias); 27 Sep 2002 15:41:50 -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 31271 invoked from network); 27 Sep 2002 15:41:49 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 27 Sep 2002 15:41:49 -0000 Received: from toenail.toronto.redhat.com (toenail.toronto.redhat.com [172.16.14.211]) by touchme.toronto.redhat.com (Postfix) with ESMTP id F1D308003E4; Fri, 27 Sep 2002 11:41:48 -0400 (EDT) Received: (from fche@localhost) by toenail.toronto.redhat.com (8.11.6/8.11.6) id g8RFfmF17728; Fri, 27 Sep 2002 11:41:48 -0400 Date: Fri, 27 Sep 2002 08:41:00 -0000 From: "Frank Ch. Eigler" To: Michael Chapman Cc: cgen@sources.redhat.com Subject: Re: Weirdness in disassembly Message-ID: <20020927114148.D17426@redhat.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="1sNVjLsmu1MXqwQ/" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from Michael.Chapman@synopsys.com on Fri, Sep 27, 2002 at 05:19:33PM +0200 X-SW-Source: 2002-q3/txt/msg00080.txt.bz2 --1sNVjLsmu1MXqwQ/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 855 Hi - On Fri, Sep 27, 2002 at 05:19:33PM +0200, Michael Chapman wrote: > [...] > My mistake somewhere. Not sure when though. The opcode=20 > for the 32 bit instruction is the same as that for=20 > the 16 bit variant of it (well it was in how I had typed > it)!=20 >=20 > Fixed that now. And I now get the correct disassembly. Good stuff. CGEN would benefit from improved detection of this sort of error. If you were to generate a simulator kernel, you'd have been told of the ambiguity. > Now what values should I have for the instruction lengths? > Obviously at least one of them has to be 16 bits for > not skipping over to much when decoding junk. Since a real program should not contain junk, a specific choice for the other variables is not that important. Go with whatever working numbers you prefer. The base-insn-size is the biggie. - FChE --1sNVjLsmu1MXqwQ/ Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 232 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9lHw8VZbdDOm/ZT0RAkSLAJ98v4cyclWWFhEHVuaIfjeIvqFP0QCeLm1X 8195VH6F3tV1bMB5HIL8wt0= =TwAm -----END PGP SIGNATURE----- --1sNVjLsmu1MXqwQ/--