public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: "\"Seongbae Park (???, ???)\"" <seongbae.park@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	  "Bonzini, Paolo" <bonzini@gnu.org>
Subject: Re: [PATCH] proper dataflow block visitation order
Date: Sat, 09 Feb 2008 03:40:00 -0000	[thread overview]
Message-ID: <47AD0130.8040304@naturalbridge.com> (raw)
In-Reply-To: <ab3a61990802081707p22da0980rda3d184f66963267@mail.gmail.com>

Seongbae Park (???, ???) wrote:
> This is an embarrassing mistake on my part that I only noticed this week,
> where we were using wrong block visit orders for dataflow analysis
> i.e. for forward problem, reverse postorder is the best known
> but we have been using postorder of inverted graph,
> and for backward problem, we should have used reverse postorder of
> inverted graph
> but we've been using postorder (of non-inverted).
>
> Two mistakes (of not reversing the postorder, and using wrong graph direction)
> canceled each other somewhat which made this mistake not noticeable
> for this long.
> The following patch reduces the total number of block visits during
> dataflow by about 4%
> building cc1 on i686, and it also reduces the block visits for the
> testcases in PR34400.
>
> While this is an overall win, there are cases where this patch increases
> the number of visits - I'll have to look at them further later,
> but clearly this is the right thing to do for now.
>
> Bootstrapped on i686 with c/c++ and no regression.
> While this is not exactly a regression,
> I'd like to commit this to 4.3 -
> as it's a fairly safe change (famous last word :).
> On the other hand, this is only a compile time fix
> and not a high-impact one at that,
> so I don't have very strong opinion on this.
>
> Seongbae
>
>
> 2008-02-08  Seongbae Park <seongbae.park@gmail.com>
>
>         * df-core.c (reverse_array, df_compute_postoder): New functions.
>         (rest_of_handle_df_initialize): Refactored
>         to call df_compute_postorder.
>         (df_analyze): Refactored to call df_compute_postorder.
>         Pass proper ordering for forward and backward problems.
>         (df_get_postorder): Return the correct block ordering.
>         (df_compact_blocks): Call df_compute_postorder.
>   
Does this effect the issues that were raised in pr34400?

this is clearly ok for 4.4. At this point mark mitchel has to approve it
for 4.3 and i assume the answer is no.

kenny

  reply	other threads:[~2008-02-09  1:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09  1:26 Seongbae Park (박성배, 朴成培)
2008-02-09  3:40 ` Kenneth Zadeck [this message]
2008-02-09 14:11 ` Paolo Bonzini
2008-02-09 16:07   ` Kenneth Zadeck
2008-02-09 16:11     ` Paolo Bonzini
2008-02-09 16:15       ` Kenneth Zadeck
2008-02-09 16:22         ` Paolo Bonzini
2008-02-09 16:39           ` Kenneth Zadeck
2008-02-10 22:36             ` Richard Guenther
2008-02-11  7:06               ` Mark Mitchell
2008-02-09 13:44 Steven Bosscher
2008-02-10  0:09 Bradley Lucier

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=47AD0130.8040304@naturalbridge.com \
    --to=zadeck@naturalbridge.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=seongbae.park@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).