This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RFC: MIPS paired single vector support

From: Richard Henderson <rth at redhat dot com>
To: James E Wilson <wilson at specifixinc dot com>
Cc: "Fu, Chao-Ying" <fu at mips dot com>, gcc-patches at gcc dot gnu dot org, David Ung <davidu at mips dot com>, Nigel Stephens <nigel at mips dot com>, "Uhler, Mike" <uhler at mercury dot mips dot com>, "Thekkath, Radhika" <radhika at mercury dot mips dot com>
Date: Wed, 18 Aug 2004 12:58:55 -0700
Subject: Re: RFC: MIPS paired single vector support
References: <3CB54817FDF733459B230DD27C690CEC041BFD@Exchange.MIPS.COM> <1092807012.15691.142.camel@aretha.corp.specifixinc.com> <20040818085927.GC25345@redhat.com> <1092857676.21700.47.camel@aretha.corp.specifixinc.com>

On Wed, Aug 18, 2004 at 12:34:36PM -0700, James E Wilson wrote:
> There is also the problem that there is no guarantee that we will have a
> type here.  If this is a libcall, we may have only modes for the
> arguments.  If there is no type, and there is no vector mode, then we
> can't get the ABI right in this case if we want them passed in FP regs. 
> Currently, there are no vector libcalls, but if we get serious about
> vector support, I would not be surprised if someone suggests it.

I will be adamantly opposed.

There is no reason at all to add vector *libcalls*.  All libcalls
must die.  All existing libcalls must be converted to real calls,
using proper FUNCTION_DECLs with proper types.


r~

References:
- RE: RFC: MIPS paired single vector support
  - From: James E Wilson
- Re: RFC: MIPS paired single vector support
  - From: Richard Henderson
- Re: RFC: MIPS paired single vector support
  - From: James E Wilson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]