From: Alexander Sokolov <robocop@amur.rosnet.ru>
To: Alan Modra <alan@SPRI.Levels.UniSA.Edu.Au>
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.9906230844350.4367-100000@ns.amur.rosnet.ru> (raw)
In-Reply-To: <Pine.LNX.4.10.9906221555130.30966-100000@mullet.itr.unisa.edu.au>
On Tue, 22 Jun 1999, Alan Modra wrote:
> I guess you could argue that "bswapl" should be allowed as bswap indeed
> does work on 32 bit regs. The patch to allow this is simple.
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.
--
Alexander Sokolov
System Administrator
ROSNET Komsomolsk-na-Amure
Tel./Fax: +7-095-737-6260
next prev parent 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 [this message]
1999-07-01 0:00 ` Alan Modra
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.9906230844350.4367-100000@ns.amur.rosnet.ru \
--to=robocop@amur.rosnet.ru \
--cc=alan@SPRI.Levels.UniSA.Edu.Au \
--cc=binutils@sourceware.cygnus.com \
/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).