From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>, gcc@gcc.gnu.org
Subject: Re: Problems with sibling calls
Date: Fri, 29 May 2009 16:57:00 -0000 [thread overview]
Message-ID: <4A200F7F.1060804@gmail.com> (raw)
In-Reply-To: <4A2017A0.5000800@gjlay.de>
Georg-Johann Lay wrote:
> But this will only (or is intended to) track information for the caller,
> not information needed for the callee that was gathered in the mentioned
> hooks. It can be used, of course, to exchange data between hooks
> provided with CUMULATIVE_ARGS and hooks that aren't, but it would still
> make implications on how the hooks get called in calls.c:expand_call().
You decide whether to allow sibcalls on a per-caller basis generally. All
the information needed to know how the arguments will be passed is available
at the call site, and your backend knows how arguments are passed, so it can
decide then whether the callee is also suitable or not. It shouldn't be a
significant overhead even if you have to evaluate the suitability of the same
callee multiple times in independent callers.
cheers,
DaveK
next prev parent reply other threads:[~2009-05-29 16:26 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 [this message]
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
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=4A200F7F.1060804@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=avr@gjlay.de \
--cc=gcc@gcc.gnu.org \
/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).