From: Georg-Johann Lay <avr@gjlay.de>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Problems with sibling calls
Date: Mon, 01 Jun 2009 14:03:00 -0000 [thread overview]
Message-ID: <4A23DF78.4030309@gjlay.de> (raw)
In-Reply-To: <200905301643.n4UGh0ae032149@d12av02.megacenter.de.ibm.com>
Ulrich Weigand schrieb:
> Georg-Johann Lay wrote:
>>I'd like to support sibling calls for a target where function args can
>>be passed in call-saved registers, namely AVR.
> The s390 back-end already has the very same issue. You may want to have
> a look at config/s390/s390.c:s390_call_saved_register_used and how it is
> used by s390_function_ok_for_sibcall.
Hi Ulrich,
thank's much for this hint. It's the missing link I was after.
Georg-Johann
prev parent reply other threads:[~2009-06-01 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 14:16 Georg-Johann Lay
2009-05-29 16:14 ` Dave Korn
2009-05-29 16:56 ` Georg-Johann Lay
2009-05-29 16:57 ` Dave Korn
2009-05-29 16:26 ` Ian Lance Taylor
2009-05-29 16:38 ` Georg-Johann Lay
2009-05-29 16:59 ` Dave Korn
2009-05-30 18:26 ` Ulrich Weigand
2009-06-01 14:03 ` Georg-Johann Lay [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=4A23DF78.4030309@gjlay.de \
--to=avr@gjlay.de \
--cc=gcc@gcc.gnu.org \
--cc=uweigand@de.ibm.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).