From: Chen Gang <chengang@emindsoft.com.cn>
To: Richard Henderson <rth@redhat.com>, law@redhat.com
Cc: mikestump@comcast.net, gcc-patches@gcc.gnu.org,
cmetcalf@ezchip.com, walt@tilera.com, peter.maydell@linaro.org
Subject: Re: [PATCH v2] gcc/config/tilegx/tilegx.c (tilegx_function_profiler): Save r10 to stack before call mcount
Date: Sat, 04 Jun 2016 13:04:00 -0000 [thread overview]
Message-ID: <5752D336.2000106@emindsoft.com.cn> (raw)
In-Reply-To: <7d7216cc-352e-e365-eae8-1abd3f26dda0@redhat.com>
On 6/3/16 09:21, Richard Henderson wrote:
> On 06/02/2016 03:23 PM, chengang@emindsoft.com.cn wrote:
>> fprintf (file,
>> + "\t{\n"
>> + "\taddi\tsp, sp, -8\n"
>> + "\tst\tsp, r10\n"
>> + "\t}\n"
>> "\t{\n"
>
> You need only do this if cfun->static_chain_decl is set.
>
OK, thanks, I shall send patch v3 for it, within this week end.
Thanks.
--
Chen Gang (陈刚)
Managing Natural Environments is the Duty of Human Beings.
prev parent reply other threads:[~2016-06-04 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 22:23 chengang
2016-06-03 1:21 ` Richard Henderson
2016-06-04 13:04 ` Chen Gang [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=5752D336.2000106@emindsoft.com.cn \
--to=chengang@emindsoft.com.cn \
--cc=cmetcalf@ezchip.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=mikestump@comcast.net \
--cc=peter.maydell@linaro.org \
--cc=rth@redhat.com \
--cc=walt@tilera.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).