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: where are caller-save addresses legitimized?

From: Jeff Law <law at redhat dot com>
To: Greg McGary <greg dot mcgary at ericsson dot com>
Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Fri, 07 May 2010 15:16:16 -0600
Subject: Re: where are caller-save addresses legitimized?
References: <4BE20304.6020906@ericsson.com> <4BE235A2.6050900@redhat.com> <4BE238D6.5040703@ericsson.com> <4BE24519.3000006@redhat.com> <4BE47E08.70505@ericsson.com>

On 05/07/10 14:54, Greg McGary wrote:

Unfortunately, that didn't yield any clues. I'll proceed by building some well-established RISCy target and see what it does in similar circumstances.

The canonical testcase for caller-save on risc targets was sparc FP code -- the older sparcs didn't have any call-saved FP regs.

Jeff

References:
- where are caller-save addresses legitimized?
  - From: Greg McGary
- Re: where are caller-save addresses legitimized?
  - From: Jeff Law
- Re: where are caller-save addresses legitimized?
  - From: Greg McGary
- Re: where are caller-save addresses legitimized?
  - From: Jeff Law
- Re: where are caller-save addresses legitimized?
  - From: Greg McGary

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