From: Segher Boessenkool <segher@kernel.crashing.org>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [rs6000] Fix ICE with -fstack-limit-register and large frames
Date: Sat, 03 Jun 2017 19:56:00 -0000 [thread overview]
Message-ID: <20170603195654.GD19687@gate.crashing.org> (raw)
In-Reply-To: <2344035.ZvlJBgxmTA@polaris>
On Sat, Jun 03, 2017 at 12:34:21PM +0200, Eric Botcazou wrote:
> > Because you cannot during reload, or another reason? We always use LRA
> > on powerpc nowadays, and LRA can deal with this.
>
> Because you cannot during prologue/epilogue generation.
Ah, this code is generated only then, I see now.
> > Only the first hunk (rs6000.md) applies, the rest is ignored (there is a
> > blank line here instead of a diff header).
>
> !?? The patch contains a single hunk for config/rs6000/rs6000.c.
The second hunk is the testcase. I now see it isn't even part of the
patch, just pasted on.
I opened PR80966. Thanks,
Segher
prev parent reply other threads:[~2017-06-03 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 7:53 Eric Botcazou
2017-05-26 13:25 ` Segher Boessenkool
2017-06-02 8:27 ` Eric Botcazou
2017-06-02 16:25 ` Segher Boessenkool
2017-06-03 10:34 ` Eric Botcazou
2017-06-03 19:56 ` Segher Boessenkool [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=20170603195654.GD19687@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.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).