linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "Cameron, Steve" <Steve.Cameron@hp.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Unrecognized opcode: `mtdcr'
Date: Wed, 29 May 2002 13:43:50 -0700	[thread overview]
Message-ID: <20020529134350.A3960@home.com> (raw)
In-Reply-To: <20020529195429.GP5997@opus.bloom.county>; from trini@kernel.crashing.org on Wed, May 29, 2002 at 12:54:29PM -0700


On Wed, May 29, 2002 at 12:54:29PM -0700, Tom Rini wrote:
>
> On Wed, May 29, 2002 at 02:30:16PM -0500, Cameron, Steve wrote:
> > [..snip...]
> > >
> > > I think we need to change arch/ppc/Makefile from:
> > > ifdef CONFIG_40x
> > > CFLAGS := $(CFLAGS) -Wa,-m405
> > > endif
> > >
> > > To:
> > > ifdef CONFIG_4xx
> > > CFLAGS := $(CFLAGS) -Wa,-m405
> > > endif
> >
> > Ok, this worked for me.  Thanks!  (I guess I wasn't so
> > far off track after all.)

Pushed this.

> > > For the moment.  Until there's some 440-specific opcodes we use (are
> > > there any?) which means we'll need to do -Wa,-m440.
> >
> > When I had tried "-Wa,-m440" before, it wasn't recognized as an option.
> > (but perhaps by "do -Wa,-m440", you mean enhance the C compiler and/or
> > assembler.)
>
> Well, iff there's 440-specific opcodes, at somepoint gas will know about
> them, and we can use -Wa,-m440, or so.  But for now -Wa,-m405 seems
> correct for 4xx.

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.

When I push some CONFIG_BOOKE cleanup we'll have an option to enable
-mbooke with as well.  That's where most of the new instructions
come from, but they aren't 440 specific (they'll be on the e500
Book E core as well).  Right now, the important booke opcodes
are picked up by the PPC403 conf in gas so there's not a huge
hurry.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-05-29 20:43 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 [this message]
2002-05-29 20:54     ` Matt Porter
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=20020529134350.A3960@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 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 NNTP newsgroup(s).