From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19575 invoked by alias); 27 Jun 2002 22:02:45 -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 19548 invoked from network); 27 Jun 2002 22:02:42 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 27 Jun 2002 22:02:42 -0000 Received: from toenail.toronto.redhat.com (unknown [172.16.14.211]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 9CB33B8049; Thu, 27 Jun 2002 18:02:41 -0400 (EDT) Received: (from fche@localhost) by toenail.toronto.redhat.com (8.11.6/8.11.6) id g5RM2e417749; Thu, 27 Jun 2002 18:02:40 -0400 Date: Thu, 27 Jun 2002 15:02:00 -0000 From: "Frank Ch. Eigler" To: Doug Evans Cc: Hans-Peter Nilsson , cgen@sources.redhat.com Subject: Re: [RFA:] Fix for lsb0? in -gen-extract-word, take 3. Message-ID: <20020627180239.D16150@redhat.com> References: <200206251137.NAA29644@ignucius.axis.se> <15643.25203.639681.481130@casey.transmeta.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="XWOWbaMNXpFDWE00" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <15643.25203.639681.481130@casey.transmeta.com>; from dje@transmeta.com on Thu, Jun 27, 2002 at 12:07:31PM -0700 X-SW-Source: 2002-q2/txt/msg00051.txt.bz2 --XWOWbaMNXpFDWE00 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 779 Hi - On Thu, Jun 27, 2002 at 12:07:31PM -0700, Doug Evans wrote: > [...] > > Perhaps it can let some of those > > unknown ports which currently must kludge "lsb0? =3D=3D #f" to now > > define "lsb0? =3D=3D #t"? >=20 > It's unfortunate such ports didn't forge ahead with the correct > choice and work through the bugs. [...] Well, crafty as that sounds, it is the case that if someone chooses to model a chip with lsb0=3D#f, and use cgen in that better-defined regime, then a patch that breaks that regime is suspect. Merely labelling the status quo an "incorrect choice" doesn't quite satisfy the burden of proof. Anyway, this is all moot until we test some of the more adventurous targets. Once HP's patches are all in, we can run some tests and report back. - FChE --XWOWbaMNXpFDWE00 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 iD8DBQE9G4t/VZbdDOm/ZT0RAgYBAJ92JjaGxioF8dvc7fkbbbDmCX4RpgCeIPbA Pg2AK4d4pg5UdoAdSq5Q3gg= =gGgZ -----END PGP SIGNATURE----- --XWOWbaMNXpFDWE00--