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: apply_result_size vs FUNCTION_VALUE_REGNO_P

From: David Edelsohn <dje at watson dot ibm dot com>
To: Richard Earnshaw <Richard dot Earnshaw at arm dot com>, Eric Botcazou <ebotcazou at libertysurf dot fr>, Eric Christopher <echristo at redhat dot com>
Cc: gcc at gcc dot gnu dot org
Date: Thu, 07 Apr 2005 10:51:00 -0400
Subject: Re: apply_result_size vs FUNCTION_VALUE_REGNO_P
References: <200504071549.01888.ebotcazou@libertysurf.fr> <1112884409.8850.21.camel@pc960.cambridge.arm.com>

>>>>> Richard Earnshaw writes:

>> I think the change breaks  __builtin_apply/__builtin_return on every platform 
>> that can return values in several contiguous registers, because the entry for 
>> FUNCTION_VALUE_REGNO_P in the manual reads:

Richard> That was my thoughts too.  You could take a look at how I fixed it on
Richard> ARM.

	Why should every target need to fix this individually?

David

Follow-Ups:
- Re: apply_result_size vs FUNCTION_VALUE_REGNO_P
  - From: Richard Earnshaw

References:
- apply_result_size vs FUNCTION_VALUE_REGNO_P
  - From: Eric Botcazou
- Re: apply_result_size vs FUNCTION_VALUE_REGNO_P
  - From: Richard Earnshaw

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