From: Paul Brook <paul@codesourcery.com>
To: binutils@sources.redhat.com
Cc: Zack Weinberg <zack@codesourcery.com>,
binutils <binutils@sourceware.org>
Subject: Re: Thumb32 assembler (58/69)
Date: Tue, 26 Apr 2005 16:34:00 -0000 [thread overview]
Message-ID: <200504261732.23055.paul@codesourcery.com> (raw)
Message-ID: <20050426163400.cHvPhCjK0PQcygRq0nnQ0C58g8UaQ7YBKrFGG7HHkPo@z> (raw)
In-Reply-To: <873btdsvpz.fsf@codesourcery.com>
On Tuesday 26 April 2005 11:01, Zack Weinberg wrote:
> More ARM/Thumb syntax compatibility: teach the ARM encoders to handle
> an omitted second oprand, and adjust the way three-operand Thumb MUL
> works (it's the third, not the second, operand that needs to equal the
> first).
Unfortunately gcc (incorrectly) outputs the three argument form
mul rd, rd, rm
I'll fix gcc, but I guess we want to support this for backwards compatibility.
Paul
next prev parent reply other threads:[~2005-04-26 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 10:18 Zack Weinberg
2005-04-26 16:32 ` Paul Brook [this message]
2005-04-26 16:34 ` Paul Brook
2005-04-26 17:03 ` Richard Earnshaw
2005-04-26 17:07 ` Richard Earnshaw
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=200504261732.23055.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=binutils@sourceware.org \
--cc=zack@codesourcery.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).