From: Joel Sherrill <joel@merlin.gcs.redstone.army.mil>
To: gas2@cygnus.com
Subject: m68k -- extb.l instruction
Date: Thu, 21 Mar 1996 12:33:00 -0000 [thread overview]
Message-ID: <Pine.SV4.3.91.960321135807.16384G-100000@merlin> (raw)
While incorporating a 68360 board support package into RTEMS and updating
tools, I tripped across this and wanted some feedback. For CPUs w/o a
bfffo instruction RTEMS has an SW implementation of bfffo which uses an
extb.l instruction. This worked correctly AFAIK for the 68000 and 68302
based BSPs using binutils 2.5.2. As of binutils 2.6, this instruction was
restricted to 020up and cpu32 which agrees with the m68k family
programmer's reference manual. But this leaves me confused -- what was
actually being generated binutils 2.5.2 on the 68000/68302? The code it
generated worked. Is this a hole in the m68k docs or just a fluke? Does
this instruction really exist on the 68302?
Just curious.
--joel
next reply other threads:[~1996-03-21 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-21 12:33 Joel Sherrill [this message]
1996-03-21 13:00 ` Ian Lance Taylor
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.SV4.3.91.960321135807.16384G-100000@merlin \
--to=joel@merlin.gcs.redstone.army.mil \
--cc=gas2@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).