public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: amodra@bigpond.net.au
Cc: tg@66h.42h.de, binutils@sources.redhat.com
Subject: Re: [RFC/RFA] Proper mnemonics for VIA PadLock (i386) instructions
Date: Sat, 16 Apr 2005 11:40:00 -0000	[thread overview]
Message-ID: <200504161140.j3GBe06L019780@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050414012555.GB5968@bubble.modra.org> (message from Alan Modra on Thu, 14 Apr 2005 10:55:55 +0930)

   Date: Thu, 14 Apr 2005 10:55:55 +0930
   From: Alan Modra <amodra@bigpond.net.au>

   On Wed, Apr 13, 2005 at 03:20:25PM +0000, Thorsten Glaser wrote:
   > DOES it fail then?

   :)  Note that I carefully said "Something like" the example I posted.

   I know that we had trouble in the past with the assembler pre-processor
   stripping whitespace completely (see tc_symbol_chars), but it may be
   that this can't happen now for the mnemonic part of an assembly line.

All tc_symbol_chars does is add a few more characters, including '-'
to the LEX_IS_SYMBOL_COMPONENT "class".  Since the alphanumeric
characters are already marked as LEX_IS_SYMBOL_COMPONENT, is exactly
the reason why the whitespace isn't stripped.  It makes us go from
state 3 to state 9 to state 10, which outputs a space, so whitespace
around the mnemonic (which is considered to be the first operand in
presence of a prefix) is conserved (even if '-' is the first or last
character of the operand.

   If one of the proponents of this patch analyse app.c behaviour enough to
   give a reasonable level of confidence, I'll accept the patch.

Does this give enough confidence?

Mark

  reply	other threads:[~2005-04-16 11:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s25d1e96.084@emea1-mh.id2.novell.com>
2005-04-13 15:20 ` Thorsten Glaser
2005-04-14  1:26   ` Alan Modra
2005-04-16 11:40     ` Mark Kettenis [this message]
2005-04-18  4:44       ` Alan Modra
2005-04-18 21:01         ` Mark Kettenis
2005-04-13 23:35 Marc Espie
  -- strict thread matches above, loose matches on Subject: below --
2005-04-13 12:29 Jan Beulich
2005-04-12 19:15 Mark Kettenis
2005-04-12 20:32 ` Michal Ludvig
2005-04-12 20:43   ` Mark Kettenis
2005-04-13  0:38     ` Alan Modra
2005-04-13 10:43       ` Thorsten Glaser
2005-04-13 18:55       ` Mark Kettenis
2005-04-13 19:29         ` H. J. Lu
2005-04-13 19:51           ` Mark Kettenis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200504161140.j3GBe06L019780@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=tg@66h.42h.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).