This is the mail archive of the gcc@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: Irix calling conventions for complex numbers

From: Eric Christopher <echristo at redhat dot com>
To: "Billinghurst, David (CALCRTS)" <david dot billinghurst at comalco dot riotinto dot com dot au>
Cc: gcc at gcc dot gnu dot org, fortran at gcc dot gnu dot org, Richard Sandiford <rsandifo at redhat dot com>
Date: Tue, 06 Jul 2004 22:56:12 -0700
Subject: Re: Irix calling conventions for complex numbers
References: <8ED2FA87C8ACC04192709688DDFD5F5F436321@calttsv025.cal.riotinto.org> <1089179330.13803.7.camel@dzur.sfbay.redhat.com>

> 
> > Where in gcc do I look to see if this is the case?
> 
>  if (GET_MODE_CLASS (mode) == MODE_COMPLEX_FLOAT
>       && GET_MODE_SIZE (mode) <= UNITS_PER_HWFPVALUE * 2)
>     return mips_return_fpr_pair (mode,
>                                  GET_MODE_INNER (mode), 0,
>                                  GET_MODE_INNER (mode),
>                                  GET_MODE_SIZE (mode) / 2);
> 
> from mips_function_value.

Bah. I meant more than this...

There's also mips_arg_info which talks about argument passing for a
single argument and where that argument needs to reside. Also from there
look at function_arg_advance.

-eric

-- 
Eric Christopher <echristo@redhat.com>

References:
- Irix calling conventions for complex numbers
  - From: Billinghurst, David (CALCRTS)
- Re: Irix calling conventions for complex numbers
  - From: Eric Christopher

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