From: Segher Boessenkool <segher@kernel.crashing.org>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/3] cfgcleanup: Bugfix in try_simplify_condjump
Date: Tue, 03 May 2016 21:09:00 -0000 [thread overview]
Message-ID: <20160503210929.GB30667@gate.crashing.org> (raw)
In-Reply-To: <CABu31nO-E4h0-AtbT=m=-Lmyk+KHFa+DSApReHvrxgbxptpquQ@mail.gmail.com>
On Tue, May 03, 2016 at 10:28:37PM +0200, Steven Bosscher wrote:
> On Tue, May 3, 2016 at 8:59 AM, Segher Boessenkool wrote:
> > If the jump_block here contains just a return, we will crash later
> > in invert_jump. Don't allow that case.
>
> But if jump_block contains a return, then it isn't the EXIT_BLOCK for
> the function.
The single successor block of the jump block is the exit block.
Too many blocks here ;-)
Segher
next prev parent reply other threads:[~2016-05-03 21:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 7:02 [PATCH 0/3] Simplify the simple_return handling Segher Boessenkool
2016-05-03 7:03 ` [PATCH 3/3] shrink-wrap: Remove complicated simple_return manipulations Segher Boessenkool
2016-05-09 13:54 ` Christophe Lyon
2016-05-09 15:08 ` Segher Boessenkool
2016-05-11 11:52 ` Jiong Wang
2016-06-14 14:54 ` [Patch, cfg] Improve jump to return optimization for complex return Jiong Wang
2016-06-14 20:30 ` Segher Boessenkool
2016-06-15 17:01 ` Jiong Wang
2016-05-03 7:03 ` [PATCH 1/3] cfgcleanup: Bugfix in try_simplify_condjump Segher Boessenkool
2016-05-03 20:29 ` Steven Bosscher
2016-05-03 21:09 ` Segher Boessenkool [this message]
2016-05-03 7:03 ` [PATCH 2/3] cfgcleanup: Fold jumps and conditional branches with returns Segher Boessenkool
2016-05-10 19:34 ` Christophe Lyon
2016-05-10 23:26 ` Segher Boessenkool
2016-05-11 8:17 ` Christophe Lyon
2016-05-03 12:53 ` [PATCH 0/3] Simplify the simple_return handling Bernd Schmidt
2016-05-03 13:31 ` Segher Boessenkool
2016-05-03 13:46 ` Bernd Schmidt
2016-05-04 0:10 ` Segher Boessenkool
2016-05-04 12:37 ` Bernd Schmidt
2016-05-03 15:03 ` Kyrill Tkachov
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=20160503210929.GB30667@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=stevenb.gcc@gmail.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).