From: Chen Gang <chengang@emindsoft.com.cn>
To: chengang@emindsoft.com.cn, law@redhat.com
Cc: rth@redhat.com, mikestump@comcast.net, gcc-patches@gcc.gnu.org,
cmetcalf@ezchip.com, walt@tilera.com, peter.maydell@linaro.org,
Chen Gang <gang.chen.5i5j@gmail.com>
Subject: Re: [PATCH v3] gcc/config/tilegx/tilegx.c (tilegx_function_profiler): Save r10 to stack before call mcount
Date: Thu, 06 Oct 2016 13:45:00 -0000 [thread overview]
Message-ID: <57F6573F.5010003@emindsoft.com.cn> (raw)
In-Reply-To: <1465046750-3021-1-git-send-email-chengang@emindsoft.com.cn>
Hello Maintainers:
Is this patch OK? Please help check it when you have time (at least for
me, it passes all related test and comparation).
And I shall continue to find and fix another issues about tilegx.
Thanks.
On 6/4/16 21:25, chengang@emindsoft.com.cn wrote:
> From: Chen Gang <gang.chen.5i5j@gmail.com>
>
> r10 may also be as parameter stack pointer for the nested function, so
> need save it before call mcount.
>
> Also clean up code: use '!' instead of "== 0" for checking
> static_chain_decl and compute_total_frame_size.
>
> 2016-06-04 Chen Gang <gang.chen.5i5j@gmail.com>
>
> gcc/
> PR target/71331
> * config/tilegx/tilegx.c (tilegx_function_profiler): Save r10
> to stack before call mcount.
> (tilegx_can_use_return_insn_p): Clean up code.
> ---
> gcc/config/tilegx/tilegx.c | 20 ++++++++++++++++++--
> 1 file changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/gcc/config/tilegx/tilegx.c b/gcc/config/tilegx/tilegx.c
> index 06c832c..55161bb 100644
> --- a/gcc/config/tilegx/tilegx.c
> +++ b/gcc/config/tilegx/tilegx.c
> @@ -3880,8 +3880,8 @@ bool
> tilegx_can_use_return_insn_p (void)
> {
> return (reload_completed
> - && cfun->static_chain_decl == 0
> - && compute_total_frame_size () == 0
> + && !cfun->static_chain_decl
> + && !compute_total_frame_size ()
> && tilegx_current_function_is_leaf ()
> && !crtl->profile && !df_regs_ever_live_p (TILEGX_LINK_REGNUM));
> }
> @@ -5507,6 +5507,15 @@ tilegx_function_profiler (FILE *file, int labelno ATTRIBUTE_UNUSED)
> fprintf (file, "\t}\n");
> }
>
> + if (cfun->static_chain_decl)
> + {
> + fprintf (file,
> + "\t{\n"
> + "\taddi\tsp, sp, -8\n"
> + "\tst\tsp, r10\n"
> + "\t}\n");
> + }
> +
> if (flag_pic)
> {
> fprintf (file,
> @@ -5524,6 +5533,13 @@ tilegx_function_profiler (FILE *file, int labelno ATTRIBUTE_UNUSED)
> "\t}\n", MCOUNT_NAME);
> }
>
> + if (cfun->static_chain_decl)
> + {
> + fprintf (file,
> + "\taddi\tsp, sp, 8\n"
> + "\tld\tr10, sp\n");
> + }
> +
> tilegx_in_bundle = false;
> }
>
>
--
Chen Gang (éå)
Managing Natural Environments is the Duty of Human Beings.
--
Chen Gang (éå)
Managing Natural Environments is the Duty of Human Beings.
next prev parent reply other threads:[~2016-10-06 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 13:26 chengang
2016-10-06 13:45 ` Chen Gang [this message]
2016-10-19 22:42 ` Jeff Law
2016-10-21 22:16 ` Chen Gang
2016-10-22 22:59 ` Chris Metcalf
2016-10-23 18:11 Bernd Edlinger
2016-10-24 15:28 ` Jeff Law
2016-10-29 4:26 ` Chen Gang
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=57F6573F.5010003@emindsoft.com.cn \
--to=chengang@emindsoft.com.cn \
--cc=cmetcalf@ezchip.com \
--cc=gang.chen.5i5j@gmail.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).