From: Matt Porter <porter@cox.net>
To: Matt Porter <porter@cox.net>
Cc: Tom Rini <trini@kernel.crashing.org>,
"Cameron, Steve" <Steve.Cameron@hp.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Unrecognized opcode: `mtdcr'
Date: Wed, 29 May 2002 13:54:28 -0700 [thread overview]
Message-ID: <20020529135428.B3960@home.com> (raw)
In-Reply-To: <20020529134350.A3960@home.com>; from porter@cox.net on Wed, May 29, 2002 at 01:43:50PM -0700
On Wed, May 29, 2002 at 01:43:50PM -0700, Matt Porter wrote:
> There is _a_ 440-specific opcode, dlbmnz. It's not yet supported by
> gas (and ideally glibc). For now, a 405 enabled toolchain is
> sufficient.
Heh, can't type...the opcode is dlmzb.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-29 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 19:30 Unrecognized opcode: `mtdcr' Cameron, Steve
2002-05-29 19:54 ` Tom Rini
2002-05-29 20:43 ` Matt Porter
2002-05-29 20:54 ` Matt Porter [this message]
2002-05-29 22:23 ` Memory usage Owen Green
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 18:48 Unrecognized opcode: `mtdcr' Stephen Cameron
2002-05-29 19:05 ` Tom Rini
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=20020529135428.B3960@home.com \
--to=porter@cox.net \
--cc=Steve.Cameron@hp.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.