From: David Edelsohn <dje.gcc@gmail.com>
To: Alan Modra <amodra@gmail.com>
Cc: "Lynn A. Boger" <laboger@linux.vnet.ibm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR66870 ppc64le, ppc64 split stack
Date: Fri, 31 Jul 2015 09:31:00 -0000 [thread overview]
Message-ID: <CAGWvnykhSUiN4NREQ2_zK4fR8b8D13ozV=SxqYSvG8A5FbQQLw@mail.gmail.com> (raw)
In-Reply-To: <20150731040010.GU26017@bubble.grove.modra.org>
On Fri, Jul 31, 2015 at 12:00 AM, Alan Modra <amodra@gmail.com> wrote:
> On Thu, Jul 30, 2015 at 03:30:12PM -0500, Lynn A. Boger wrote:
>> PR66870
>> * gcc/config/rs6000/rs6000.c: Add check for no_split_stack
>> function attribute along with flag_split_stack check to
>> determine when to generate split stack prologue for
>> ppc64 and ppc64le.
>
> Looks good to me, except that the changelog entry should mention the
> modified functions, for example:
>
> PR target/66870
> * gcc/config/rs6000/rs6000.c (rs6000_emit_prologue): Check for
> no_split_stack function attribute along with flag_split_stack.
> (rs6000_expand_split_stack_prologue): Likewise.
>
> Also, formatting rules for gcc say to not split a line after an
> operator.
>
>> + int using_split_stack = flag_split_stack &&
>> + (lookup_attribute ("no_split_stack", DECL_ATTRIBUTES (cfun->decl))
>> + == NULL);
>
> The "&&" belongs on the next line, with parentheses added so that emacs
> and indent will line up the continuation nicely.
>
> int using_split_stack = (flag_split_stack
> && (lookup_attribute ("no_split_stack",
> DECL_ATTRIBUTES (cfun->decl))
> == NULL));
>
>
> David, the following is another piece of the PR66870 fixes. This
> stops shrink-wrap from moving insns around in the first few blocks of
> a function, in a way that is incorrect given that r12 is live.
> Bootstrapped and regression tested powerpc64le-linux (and
> powerpc64-linux by Lynn).
>
> PR target/66870
> * config/rs6000/rs6000.c (machine_function): Add split_stack_argp_used.
> (rs6000_emit_prologue): Set it.
> (rs6000_set_up_by_prologue): Specify r12 when split_stack_argp_used.
Both patches with your suggested changes are okay.
Thanks, David
next prev parent reply other threads:[~2015-07-31 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 21:10 Lynn A. Boger
2015-07-31 8:11 ` Alan Modra
2015-07-31 9:31 ` David Edelsohn [this message]
2015-08-05 1:22 ` Lynn Boger
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='CAGWvnykhSUiN4NREQ2_zK4fR8b8D13ozV=SxqYSvG8A5FbQQLw@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=laboger@linux.vnet.ibm.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).