From: Jeff Law <law@redhat.com>
To: Greg McGary <greg.mcgary@ericsson.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: where are caller-save addresses legitimized?
Date: Fri, 07 May 2010 21:16:00 -0000 [thread overview]
Message-ID: <4BE48320.5040408@redhat.com> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2010-05-07 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 23:45 Greg McGary
2010-05-06 3:21 ` Jeff Law
2010-05-06 3:35 ` Greg McGary
2010-05-06 4:27 ` Jeff Law
2010-05-07 20:54 ` Greg McGary
2010-05-07 21:16 ` Jeff Law [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BE48320.5040408@redhat.com \
--to=law@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=greg.mcgary@ericsson.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).