From: "Kevin D. Kissell" <kevink@mips.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>, <heinold@physik.tu-cottbus.de>,
<linux-mips@oss.sgi.com>
Subject: Re: Question concerning Assembler error
Date: Thu, 8 Mar 2001 17:54:29 +0100 [thread overview]
Message-ID: <01b701c0a7f0$79260ba0$0deca8c0@Ulysses> (raw)
In-Reply-To: 20010308174044.B11107@bacchus.dhis.org
> > Hm sorry cant help with the assembler problem, but which machine
> > has a 4600 Prozessor and run mipsel on it?
>
> RM200C.
Actually, It's far more likely that Jeff is working with a
MIPS 4KC or 5KC CPU core. -mcpu=r4600 ends up
being the closest fit to the MIPS32 ISA and pipeline
among the options available for the Linux-capable
gcc compilers.
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>,
heinold@physik.tu-cottbus.de, linux-mips@oss.sgi.com
Subject: Re: Question concerning Assembler error
Date: Thu, 8 Mar 2001 17:54:29 +0100 [thread overview]
Message-ID: <01b701c0a7f0$79260ba0$0deca8c0@Ulysses> (raw)
Message-ID: <20010308165429.CMpDQslFcFt8cvn0guz4QuM85M21vc4VyZt889-XvoA@z> (raw)
In-Reply-To: 20010308174044.B11107@bacchus.dhis.org
> > Hm sorry cant help with the assembler problem, but which machine
> > has a 4600 Prozessor and run mipsel on it?
>
> RM200C.
Actually, It's far more likely that Jeff is working with a
MIPS 4KC or 5KC CPU core. -mcpu=r4600 ends up
being the closest fit to the MIPS32 ISA and pipeline
among the options available for the Linux-capable
gcc compilers.
Kevin K.
next prev parent reply other threads:[~2001-03-08 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 16:20 Question concerning Assembler error Jeff Harrell
2001-03-08 16:30 ` H.Heinold
2001-03-08 16:40 ` Ralf Baechle
2001-03-08 16:54 ` Kevin D. Kissell [this message]
2001-03-08 16:54 ` Kevin D. Kissell
2001-03-09 0:18 ` Ralf Baechle
2001-03-09 0:18 ` Ralf Baechle
2001-03-08 16:37 ` Ralf Baechle
2001-03-08 16:43 ` mips gcc 2.95.2 and 2.91.66 bug Fabrice Bellard
2001-03-09 2:28 ` Hiroyuki Machida
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='01b701c0a7f0$79260ba0$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=heinold@physik.tu-cottbus.de \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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 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.