From: Ben Elliston <bje+dated+1148968298.35ff1c@air.net.au>
To: Richard Sandiford <richard@codesourcery.com>
Cc: binutils@sourceware.org, drow@false.org
Subject: Re: Coldfire fmovem fixes
Date: Thu, 25 May 2006 13:57:00 -0000 [thread overview]
Message-ID: <20060525155134.A16253@mailhub.air.net.au> (raw)
In-Reply-To: <20060524004418.GA1912@ozlabs.au.ibm.com>; from bje@au1.ibm.com on Wed, May 24, 2006 at 10:44:18AM +1000
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
Hi Richard
> include/opcodes/
> * m68k.h (mcf_mask): Define.
>
> opcodes/
> * m68k-opc.c (m68k_opcodes): Fix the masks of the Coldfire fmovemd
> and fmovem entries. Put register list entries before immediate
> mask entries. Use "l" rather than "L" in the fmovem entries.
> * m68k-dis.c (match_insn_m68k): Remove the PRIV argument and work it
> out from INFO.
> (m68k_scan_mask): New function, split out from...
> (print_insn_m68k): ...here. If no architecture has been set,
> first try printing an m680x0 instruction, then try a Coldfire one.
>
> gas/testsuite/
> * gas/m68k/mcf-fpu.s: Add fmovemd and fmovem instructions.
> * gas/m68k/mcf-fpu.d: Adjust accordingly.
OK. I'm undecided about whether this warrants committing to the 2.17
branch. I'll leave that to Daniel to decide.
Cheers, Ben
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2006-05-25 5:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060524004418.GA1912@ozlabs.au.ibm.com>
2006-05-25 13:57 ` Ben Elliston [this message]
2006-05-25 16:53 ` Daniel Jacobowitz
2006-05-22 15:59 Richard Sandiford
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=20060525155134.A16253@mailhub.air.net.au \
--to=bje+dated+1148968298.35ff1c@air.net.au \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=richard@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).