From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15500 invoked by alias); 13 Apr 2005 12:29:18 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 15309 invoked from network); 13 Apr 2005 12:28:55 -0000 Received: from unknown (HELO emea1-mh.id2.novell.com) (195.33.99.129) by sourceware.org with SMTP; 13 Apr 2005 12:28:55 -0000 Received: from EMEA1-MTA by emea1-mh.id2.novell.com with Novell_GroupWise; Wed, 13 Apr 2005 13:28:54 +0200 Message-Id: Date: Wed, 13 Apr 2005 12:29:00 -0000 From: "Jan Beulich" To: , Subject: Re: [RFC/RFA] Proper mnemonics for VIA PadLock (i386) instructions Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-SW-Source: 2005-04/txt/msg00312.txt.bz2 >>> Thorsten Glaser 13.04.05 12:42:35 >>> >Alan Modra dixit: > >>a high likelihood of breaking other valid assembly. The gas app.c code >>has a nasty habit of completely removing whitespace once past the >>mnemonic of an instruction, and it can get confused. Something like >> >> addr16 mov -2,%eax >> >>might fail if '-' is a valid mnemonic char. > >Can't gas be fixed, then? Sounds like the "obvious" thing to do to me. > >Alternatively, we'd need to make a way for a dash to be only >recognised as part of a mnemonic if followed by a letter. That wouldn't help either: .equiv two, 2 movl -two(%ebx), %eax would still fail.