From: Dominic Sweetman <dom@mips.com>
To: Eric Christopher <echristo@redhat.com>
Cc: Long Li <long21st@yahoo.com>, linux-mips@linux-mips.org
Cc: David Ung <davidu@mips.com>, Nigel Stephens <nigel@mips.com>
Subject: Re: gcc support of mips32 release 2
Date: Fri, 5 Mar 2004 10:12:08 +0000 [thread overview]
Message-ID: <16456.21112.570245.1011@arsenal.mips.com> (raw)
In-Reply-To: <1078478086.4308.14.camel@dzur.sfbay.redhat.com>
> > Seems to me, this mips32 release 2 is an extension of
> > mips32, added some new instructions, eg. EHB, etc. So
> > would it be necessary that gcc be updated, like what
> > gnu as has done, in the future to reflect this
> > extension?
>
> It will be in the soon to be released 3.4. Contributed by Chris
> Demetriou of Broadcom.
We added patterns to let our (old) GCC use the new rotates and
bit-insert/extracts, at least in simple cases. I'm not sure whether
we've put those in our 3.4 evolution tree yet, but if we have we
should push those out.
--
Dominic Sweetman
MIPS Technologies.
WARNING: multiple messages have this Message-ID (diff)
From: Dominic Sweetman <dom@mips.com>
To: Eric Christopher <echristo@redhat.com>
Cc: Long Li <long21st@yahoo.com>,
linux-mips@linux-mips.org, David Ung <davidu@mips.com>,
Nigel Stephens <nigel@mips.com>
Subject: Re: gcc support of mips32 release 2
Date: Fri, 5 Mar 2004 10:12:08 +0000 [thread overview]
Message-ID: <16456.21112.570245.1011@arsenal.mips.com> (raw)
Message-ID: <20040305101208.qUz3o1vHWDwiMGMgtNbjkGhoTBznRLt24RvZeDR9Pyg@z> (raw)
In-Reply-To: <1078478086.4308.14.camel@dzur.sfbay.redhat.com>
> > Seems to me, this mips32 release 2 is an extension of
> > mips32, added some new instructions, eg. EHB, etc. So
> > would it be necessary that gcc be updated, like what
> > gnu as has done, in the future to reflect this
> > extension?
>
> It will be in the soon to be released 3.4. Contributed by Chris
> Demetriou of Broadcom.
We added patterns to let our (old) GCC use the new rotates and
bit-insert/extracts, at least in simple cases. I'm not sure whether
we've put those in our 3.4 evolution tree yet, but if we have we
should push those out.
--
Dominic Sweetman
MIPS Technologies.
next prev parent reply other threads:[~2004-03-05 10:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 7:55 gcc support of mips32 release 2 Long Li
2004-03-05 9:14 ` Eric Christopher
2004-03-05 10:12 ` Dominic Sweetman [this message]
2004-03-05 10:12 ` Dominic Sweetman
2004-03-05 17:03 ` Long Li
2004-03-08 11:11 ` Dominic Sweetman
2004-03-08 12:15 ` David Ung
2004-03-08 17:45 ` Eric Christopher
2004-03-18 13:18 ` Maciej W. Rozycki
2004-03-18 14:10 ` Dominic Sweetman
2004-03-18 21:19 ` Ralf Baechle
2004-03-19 13:44 ` Maciej W. Rozycki
2004-03-22 9:42 ` Dominic Sweetman
2004-03-22 11:14 ` Maciej W. Rozycki
2004-03-22 14:49 ` Dominic Sweetman
2004-03-22 16:19 ` Michael Uhler
2004-03-18 16:52 ` Michael Uhler
2004-03-18 21:37 ` Ralf Baechle
2004-03-19 10:42 ` Geert Uytterhoeven
2004-03-19 12:55 ` Ralf Baechle
2004-03-24 12:38 ` Goswin von Brederlow
2004-03-24 13:52 ` Ralf Baechle
2004-03-24 17:57 ` Dominic Sweetman
2004-03-19 13:47 ` 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=16456.21112.570245.1011@arsenal.mips.com \
--to=dom@mips.com \
--cc=echristo@redhat.com \
--cc=linux-mips@linux-mips.org \
--cc=long21st@yahoo.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