From: Eric Christopher <echristo@redhat.com>
To: linux-mips@linux-mips.org
Subject: Re: gcc support for mips32 release 2]
Date: Fri, 05 Mar 2004 14:29:38 -0800 [thread overview]
Message-ID: <1078525778.3353.2.camel@dzur.sfbay.redhat.com> (raw)
More on the thread from Chris since it was cross posted to gcc@ as well.
-eric
-----Forwarded Message-----
> From: cgd@broadcom.com
> To: long21st@yahoo.com
> Cc: gcc@gcc.gnu.org
> Subject: Re: gcc support for mips32 release 2
> Date: Fri, 05 Mar 2004 08:19:08 -0800
>
> At Fri, 5 Mar 2004 07:54:19 +0000 (UTC), "Long Li" wrote:
> > I have a question about gcc support for mips32 release
> > 2. I noticed that in gnu as(assembler) 2.14, there is
> > an option for it, but does newest gcc version support
> > mips32 release 2? I did not find it in the mips.c or
> > configure file.
>
> as others have noted, I contributed it to GCC and it should appear in
> 3.4.
>
> Note that 3.4 has only partial support for the new instructions. In
> particular, it only knows how to generate rotates and, IIRC, some of
> the sign-extend instructions. (it's been a while since i did the
> work.)
>
> It does *not* know how to do use the insert/extract instructions.
>
>
> If anybody knows of a MIPS64 release 2 implementation, I also have
> support for GCC to do that. (Problem is, the way the GCC MIPS
> back-end currently is, it really wants a processor implementation
> before a new ISA is added.)
>
> I also have a number of sim changes for 32r2 -- can't remember if i've
> integrated all of them or not, yet -- and 64r2. (Fairly sure i've not
> done the 64r2 changes.)
>
>
>
> chris
--
Eric Christopher <echristo@redhat.com>
next reply other threads:[~2004-03-05 22:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 22:29 Eric Christopher [this message]
2004-03-17 16:18 ` gcc support for mips32 release 2] Maciej W. Rozycki
2004-03-17 16:41 ` cgd
2004-03-17 18:44 ` Maciej W. Rozycki
2004-03-18 22:51 ` Ralf Baechle
2004-03-18 23:03 ` Eric Christopher
2004-03-19 14:16 ` Maciej W. Rozycki
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=1078525778.3353.2.camel@dzur.sfbay.redhat.com \
--to=echristo@redhat.com \
--cc=linux-mips@linux-mips.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