From: Carsten Langgaard <carstenl@mips.com>
To: "Zajerko-McKee, Nick" <nmckee@telogy.com>
Cc: "Linux-Mips (E-mail)" <linux-mips@oss.sgi.com>
Subject: Re: GAS 4kc question...
Date: Wed, 31 Jul 2002 08:03:54 +0200 [thread overview]
Message-ID: <3D477DC3.6C304839@mips.com> (raw)
In-Reply-To: 37A3C2F21006D611995100B0D0F9B73CBFE213@tnint11.telogy.design.ti.com
I guess you mean madd and mul (not mulu).
These instructions are MIPS32 instructions and are most likely not recognized
by your toolchain.
Try use the compiler option "-mips32" to verify it.
So for now I'm afraid you need to hardcode these by hand. We are very close to
release a MIPS32 compiler, so we don't need these hacks in the future.
/Carsten
"Zajerko-McKee, Nick" wrote:
> Hi,
>
> I'm trying to write some inline assembler code that needs the madd and mulu
> op codes found on the 4KC processor. I've tried setting the cpu to 4650,
> but it failed to recognize the mulu instruction. Can someone give me the
> magic incantation? I'm running right now GCC 2.95.3 from Montavista. I
> guess one way I can attack it for now is to build the op code by hand, but
> that is quite dirty, IMHO...
>
> ------------------------------------------------------------------------
>
> Nick Zajerko-McKee.vcfName: Nick Zajerko-McKee.vcf
> Type: VCard (text/x-vcard)
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2002-07-31 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 22:28 GAS 4kc question Zajerko-McKee, Nick
2002-07-30 23:08 ` Thiemo Seufer
2002-07-31 0:31 ` Ralf Baechle
2002-07-31 6:03 ` Carsten Langgaard [this message]
2002-07-31 7:04 ` Kevin D. Kissell
2002-07-31 7:04 ` Kevin D. Kissell
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=3D477DC3.6C304839@mips.com \
--to=carstenl@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=nmckee@telogy.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