This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] MIPS32 DSP intrinsics
- From: Paul Brook <paul at codesourcery dot com>
- To: gcc-patches at gcc dot gnu dot org
- Cc: Nigel Stephens <nigel at mips dot com>,Eric Christopher <echristo at redhat dot com>,Chao-ying Fu <fu at mips dot com>,Richard Sandiford <rsandifo at redhat dot com>,"Thekkath, Radhika" <radhika at mips dot com>
- Date: Wed, 1 Jun 2005 16:57:27 +0100
- Subject: Re: [PATCH] MIPS32 DSP intrinsics
- References: <3CB54817FDF733459B230DD27C690CEC012BAE76@Exchange.MIPS.COM> <1117640338.4744.9.camel@localhost.localdomain> <429DD991.6060201@mips.com>
On Wednesday 01 June 2005 16:51, Nigel Stephens wrote:
> Eric Christopher wrote:
> >>I'm not against adding these new
> >>instructions to the GNU simulator, it's
> >>just that this may not be possible until the new architecture documents
> >>have been made publicly available.
> >
> >I don't want to add the instructions to gcc until the architecture
> >documents are publicly available.
>
> I understand your concerns, but is this standard policy for GCC? We're
> trying to get ahead here, and make sure that when our new CPU is
> launched we have support for it in place within GCC and Binutils. We're
> not talking about a long delay before publication - on the order of two
> months.
Apart from anything else we require that all intrinsics be documented. How do
you propose to do this if the architecture details are not publicly
available?
Paul