public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: joel@merlin.gcs.redstone.army.mil
Cc: gas2@cygnus.com
Subject: Re: m68k -- extb.l instruction
Date: Thu, 21 Mar 1996 13:00:00 -0000	[thread overview]
Message-ID: <199603212100.QAA06495@sanguine.cygnus.com> (raw)
In-Reply-To: <Pine.SV4.3.91.960321135807.16384G-100000@merlin>

   Date: Thu, 21 Mar 1996 14:04:28 -0600 (CST)
   From: Joel Sherrill <joel@merlin.gcs.redstone.army.mil>

   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?  

As far as I can see from the sources, gas has always restricted the
extb.l instruction to 68020up and cpu32.  This did not change between
the 2.5.2 and 2.6 releases.  I don't know why it was working for you
for 2.5.2.

Ian


      reply	other threads:[~1996-03-21 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-21 12:33 Joel Sherrill
1996-03-21 13:00 ` Ian Lance Taylor [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=199603212100.QAA06495@sanguine.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=joel@merlin.gcs.redstone.army.mil \
    /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).