public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <alan@SPRI.Levels.UniSA.Edu.Au>
To: Alexander Sokolov <robocop@amur.rosnet.ru>
Cc: binutils@sourceware.cygnus.com
Subject: Re: Error: suffix or operands invalid for `bswap'
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.9906230943470.1129-100000@mullet.itr.unisa.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.10.9906230844350.4367-100000@ns.amur.rosnet.ru>

On Wed, 23 Jun 1999, Alexander Sokolov wrote:
> At least openssl and international kernel patch use bswapl. Rejecting
> this syntax causes compiling failure. On the other hand "bswapl %eax"
> is no less legal than "pushl %eax" or "addl %eax,%ebx" allowed in 2.9.4
> and if you disallow l suffix for bswap you should also do it for all the
> instructions with 32-bit regs.

The difference is that there are "pushw", "addw", and "addb" instructions,
but no "bswapw".  In saying this, I'm not arguing against restoring bswapl
to legal status, just pointing out that "bswap" is somewhat special.

I'll check a patch in tonight to fix bswap, unless anyone reading this
list has a violent objection.  I'm also curious to know whether Unixware
or other AT&T format x86 assemblers accept "bswapl".  Would someone with
access to such an assembler please try it out?

      reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 Alexander Sokolov
1999-07-01  0:00 ` Alan Modra
1999-07-01  0:00   ` Alexander Sokolov
1999-07-01  0:00     ` Alan Modra [this message]

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=Pine.LNX.4.10.9906230943470.1129-100000@mullet.itr.unisa.edu.au \
    --to=alan@spri.levels.unisa.edu.au \
    --cc=binutils@sourceware.cygnus.com \
    --cc=robocop@amur.rosnet.ru \
    /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).