From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
Jeff Law <law@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Richard Biener <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>,
Richard Sandiford <rdsandiford@googlemail.com>,
Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH, ARM] Add a new target hook to compute the frame layout
Date: Fri, 05 Aug 2016 15:23:00 -0000 [thread overview]
Message-ID: <AM4PR0701MB2162F870F7810D3A0909AA8DE4180@AM4PR0701MB2162.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <4b971f30-b5e2-7960-aab4-a873f3ed433e@arm.com>
On 08/05/16 16:06, Richard Earnshaw (lists) wrote:
>
> Thanks, that's pretty much what I expected would be the case.
>
> Could I suggest:
>
> This target hook is called once each time the frame layout needs to be
> recalculated. The calculations can be cached by the target and can then
> be used by @code{INITIAL_ELIMINATION_OFFSET} instead of re-computing the
> layout on every invocation of that hook. This is particularly useful
> for targets that have an expensive frame layout function. Implementing
> this callback is optional.
>
> R.
>
Excellent! I like this wording very much.
Thanks
Bernd.
next prev parent reply other threads:[~2016-08-05 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 14:47 [PATCH] " Bernd Edlinger
2016-06-21 21:30 ` Jeff Law
2016-06-22 5:12 ` Bernd Edlinger
2016-06-22 7:21 ` AW: " Bernd Edlinger
2016-06-22 18:34 ` Jeff Law
2016-06-22 18:49 ` Jeff Law
2016-06-22 20:25 ` Bernd Edlinger
2016-08-04 21:16 ` [PATCH, ARM] " Bernd Edlinger
2016-08-05 9:29 ` Richard Earnshaw (lists)
2016-08-05 12:49 ` Bernd Edlinger
2016-08-05 14:06 ` Richard Earnshaw (lists)
2016-08-05 15:23 ` Bernd Edlinger [this message]
2016-09-05 16:45 ` Bernd Edlinger
2017-05-05 15:02 ` Richard Earnshaw (lists)
2017-05-06 18:16 ` Bernd Edlinger
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=AM4PR0701MB2162F870F7810D3A0909AA8DE4180@AM4PR0701MB2162.eurprd07.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=nickc@redhat.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=rdsandiford@googlemail.com \
--cc=rguenther@suse.de \
/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).