From: Marek Polacek <polacek@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Don't bypass blocks with multiple latch edges (PR middle-end/54838)
Date: Fri, 30 Nov 2012 16:28:00 -0000 [thread overview]
Message-ID: <20121130161654.GG10621@redhat.com> (raw)
In-Reply-To: <CAFiYyc2F+cKJd9q1ytr9Ud054VMqP2jwnJKb2Eeme4qNCrRgHw@mail.gmail.com>
On Fri, Nov 30, 2012 at 10:01:37AM +0100, Richard Biener wrote:
> RTL cprop seems to run both before and after RTL loop optimizers (currently
> after RTL loop optimizers we throw away loops - an arbitrary chosen point
> before IRA across which I could not get things to work). Thus you could do
>
> if (current_loops)
> is_loop_header = bb == bb->loop_father->header;
> else
> {
> may_be_loop_header = false;
> FOR_EACH_EDGE (e, ei, bb->preds)
> if (e->flags & EDGE_DFS_BACK)
> {
> may_be_loop_header = true;
> break;
> }
> }
I can do this as a followup.
> I don't understand
>
> /* The irreducible loops created by redirecting of edges entering the
> loop from outside would decrease effectiveness of some of the
> following optimizations, so prevent this. */
> if (may_be_loop_header
> && !(e->flags & EDGE_DFS_BACK))
> {
> ei_next (&ei);
> continue;
> }
>
> why isn't this simply
>
> if (may_be_loop_header)
> {
> ei_next (&ei);
> continue;
> }
>
> ? It looks like the code tries to allow "rotating" a loop - but that's only
> good if bb has exactly two predecessors (one entry and one latch edge).
> And even then it requires to manually update the loop structures (update
> what the new header and latch blocks are).
>
> That said, removing the !(e->flags & EDGE_DFS_BACK) condition seems
> to fix the ICE. Threading across a loop header is in fact complicated
> (see the special routine tree-ssa-threadupdate.c:thread_through_loop_header
> necessary for that). Let's declare the GIMPLE level did all interesting
> threadings through headers.
Agreed. This is the fix I had some time ago, but at that time it
didn't seem like such a great idea. Done this time around.
Regtested/bootstrapped on x86_64-linux, ok for trunk?
2012-11-30 Marek Polacek <polacek@redhat.com>
PR middle-end/54838
* cprop.c (bypass_block): Skip header edges.
* gcc.dg/pr54838.c: New test.
--- gcc/cprop.c.mp 2012-11-29 15:49:53.120524295 +0100
+++ gcc/cprop.c 2012-11-30 10:30:23.509501957 +0100
@@ -1539,8 +1539,7 @@ bypass_block (basic_block bb, rtx setcc,
/* The irreducible loops created by redirecting of edges entering the
loop from outside would decrease effectiveness of some of the
following optimizations, so prevent this. */
- if (may_be_loop_header
- && !(e->flags & EDGE_DFS_BACK))
+ if (may_be_loop_header)
{
ei_next (&ei);
continue;
--- gcc/testsuite/gcc.dg/pr54838.c.mp 2012-11-26 14:48:43.783980854 +0100
+++ gcc/testsuite/gcc.dg/pr54838.c 2012-11-29 17:43:19.397737779 +0100
@@ -0,0 +1,24 @@
+/* PR middle-end/54838 */
+/* { dg-do compile } */
+/* { dg-options "-O2 -fno-forward-propagate -ftracer" } */
+
+void bar (void);
+
+void
+foo (void *b, int *c)
+{
+again:
+ switch (*c)
+ {
+ case 1:
+ if (!b)
+ {
+ bar ();
+ return;
+ }
+ goto again;
+ case 3:
+ if (!b)
+ goto again;
+ }
+}
Marek
next prev parent reply other threads:[~2012-11-30 16:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 14:28 Marek Polacek
2012-11-28 9:55 ` Eric Botcazou
2012-11-28 18:39 ` Marek Polacek
2012-11-29 8:34 ` Richard Biener
2012-11-29 8:57 ` Steven Bosscher
2012-11-29 9:35 ` Richard Biener
2012-11-29 15:39 ` Marek Polacek
2012-11-29 15:42 ` Marek Polacek
2012-11-29 15:51 ` Steven Bosscher
2012-11-29 16:56 ` Marek Polacek
2012-11-29 17:45 ` Eric Botcazou
2012-11-30 9:02 ` Richard Biener
2012-11-30 16:28 ` Marek Polacek [this message]
2012-11-30 22:01 ` Eric Botcazou
2012-11-30 22:33 ` Eric Botcazou
2012-12-01 16:18 ` Marek Polacek
2012-12-02 10:06 ` 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=20121130161654.GG10621@redhat.com \
--to=polacek@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@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).