From: Jakub Jelinek <jakub@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/3] function: Factor out make_*logue_seq
Date: Thu, 19 May 2016 07:41:00 -0000 [thread overview]
Message-ID: <20160519074140.GZ28550@tucnak.redhat.com> (raw)
In-Reply-To: <20160519072815.GA6926@gate.crashing.org>
On Thu, May 19, 2016 at 02:28:15AM -0500, Segher Boessenkool wrote:
> The following fixes it, tested on x86_64-linux. Is it okay for trunk?
>
> (It only happens for targets that have a splitter gated by epilogue_done
> for their eh_return pattern).
>
>
> Segher
>
>
> 2016-05-19 Segher Boessenkool <segher@kernel.crashing.org>
>
> * function.c (thread_prologue_and_epilogue_insn): Move the
> "goto epilogue_done" one block later.
Ok, thanks.
Jakub
next prev parent reply other threads:[~2016-05-19 7:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 1:09 [PATCH 1/3] function: Do the CLEANUP_EXPENSIVE after shrink-wrapping, not before Segher Boessenkool
2016-05-17 1:09 ` [PATCH 2/3] function: Factor out make_*logue_seq Segher Boessenkool
2016-05-17 20:35 ` Jeff Law
2016-05-18 17:17 ` H.J. Lu
2016-05-18 18:11 ` Segher Boessenkool
2016-05-18 18:20 ` H.J. Lu
2016-05-18 18:24 ` H.J. Lu
2016-05-18 18:35 ` Segher Boessenkool
2016-05-18 22:13 ` Segher Boessenkool
2016-05-19 7:16 ` Jakub Jelinek
2016-05-19 7:28 ` Segher Boessenkool
2016-05-19 7:41 ` Jakub Jelinek [this message]
2016-05-19 17:20 ` Jeff Law
2016-05-17 1:09 ` [PATCH 3/3] function: Restructure *logue insertion Segher Boessenkool
2016-05-19 8:04 ` Segher Boessenkool
2016-05-19 22:00 ` Jeff Law
2016-05-19 22:20 ` Segher Boessenkool
2016-05-20 9:28 ` Thomas Schwinge
2016-05-20 13:21 ` Thomas Schwinge
2016-05-20 14:47 ` Nathan Sidwell
2016-05-20 15:35 ` Segher Boessenkool
2016-05-20 21:27 ` Segher Boessenkool
2016-05-17 8:06 ` [PATCH 1/3] function: Do the CLEANUP_EXPENSIVE after shrink-wrapping, not before Eric Botcazou
2016-05-17 8:47 ` Segher Boessenkool
2016-05-17 9:08 ` Eric Botcazou
2016-05-17 9:18 ` Segher Boessenkool
2016-05-17 22:23 ` Segher Boessenkool
2016-05-17 22:34 ` Eric Botcazou
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=20160519074140.GZ28550@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.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).