From: David Edelsohn <dje.gcc@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jeffrey Law <law@redhat.com>
Subject: Re: [PATCH 5/5] rs6000: Separate shrink-wrapping
Date: Mon, 26 Sep 2016 18:16:00 -0000 [thread overview]
Message-ID: <CAGWvnynf2QfwwMZdAPDBYE2uCFs_y-iNQ0E_v60+-UhokSyrsw@mail.gmail.com> (raw)
In-Reply-To: <6012e775f424c60deb1a594bebca35f7515d066e.1474616087.git.segher@kernel.crashing.org>
On Fri, Sep 23, 2016 at 4:21 AM, Segher Boessenkool
<segher@kernel.crashing.org> wrote:
> This implements the hooks for separate shrink-wrapping for rs6000.
> It handles GPRs and LR. The GPRs get a component number corresponding
> to their register number; LR gets component number 0.
>
>
> 2016-09-23 Segher Boessenkool <segher@kernel.crashing.org>
>
> * config/rs6000/rs6000.c (machine_function): Add new fields
> gpr_is_wrapped_separately and lr_is_wrapped_separately.
> (TARGET_SHRINK_WRAP_GET_SEPARATE_COMPONENTS,
> TARGET_SHRINK_WRAP_COMPONENTS_FOR_BB,
> TARGET_SHRINK_WRAP_DISQUALIFY_COMPONENTS,
> TARGET_SHRINK_WRAP_EMIT_PROLOGUE_COMPONENTS,
> TARGET_SHRINK_WRAP_EMIT_EPILOGUE_COMPONENTS,
> TARGET_SHRINK_WRAP_SET_HANDLED_COMPONENTS): Define.
> (rs6000_get_separate_components): New function.
> (rs6000_components_for_bb): New function.
> (rs6000_disqualify_components): New function.
> (rs6000_emit_prologue_components): New function.
> (rs6000_emit_epilogue_components): New function.
> (rs6000_set_handled_components): New function.
> (rs6000_emit_prologue): Don't emit LR save if lr_is_wrapped_separately.
> Don't emit GPR saves if gpr_is_wrapped_separately for that register.
> (rs6000_emit_epilogue): Don't emit GPR restores if
> gpr_is_wrapped_separately for that register. Don't make a
> REG_CFA_RESTORE note for registers we did not restore, either.
The rs6000 bits are okay when the rest of the shrink-wrapping
infrastructure is approved.
Thanks, David
prev parent reply other threads:[~2016-09-26 17:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 8:22 [PATCH v3 0/5] " Segher Boessenkool
2016-09-23 8:22 ` [PATCH 1/5] separate shrink-wrap: New command-line flag, status flag, hooks, and doc Segher Boessenkool
2016-09-26 17:02 ` Jeff Law
2016-09-23 8:22 ` [PATCH 2/5] dce: Don't dead-code delete separately wrapped restores Segher Boessenkool
2016-09-26 16:55 ` Jeff Law
2016-09-23 8:23 ` [PATCH 3/5] regrename: Don't rename restores Segher Boessenkool
2016-09-26 16:44 ` Jeff Law
2016-09-23 8:33 ` [PATCH 4/5] shrink-wrap: Shrink-wrapping for separate components Segher Boessenkool
2016-09-27 21:25 ` Jeff Law
2016-09-28 9:26 ` Segher Boessenkool
2016-09-28 16:36 ` Jeff Law
2016-09-30 10:14 ` Segher Boessenkool
[not found] ` <20160930102908.GB14933@gate.crashing.org>
2016-09-30 10:52 ` Segher Boessenkool
2016-10-10 21:21 ` Jeff Law
2016-10-10 22:23 ` Segher Boessenkool
2016-09-23 8:44 ` [PATCH 5/5] rs6000: Separate shrink-wrapping Segher Boessenkool
2016-09-26 16:39 ` Jeff Law
2016-09-26 18:16 ` David Edelsohn [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=CAGWvnynf2QfwwMZdAPDBYE2uCFs_y-iNQ0E_v60+-UhokSyrsw@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=segher@kernel.crashing.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).