From: Tom Rini <trini@kernel.crashing.org>
To: "Cameron, Steve" <Steve.Cameron@hp.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Unrecognized opcode: `mtdcr'
Date: Wed, 29 May 2002 12:54:29 -0700 [thread overview]
Message-ID: <20020529195429.GP5997@opus.bloom.county> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E10640167CFD8@cceexc18.americas.cpqcorp.net>
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.)
>
> > 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.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-29 19: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 [this message]
2002-05-29 20:43 ` Matt Porter
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=20020529195429.GP5997@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=Steve.Cameron@hp.com \
--cc=linuxppc-embedded@lists.linuxppc.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).