public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Seongbae Park (박성배, 朴成培)" <seongbae.park@gmail.com>
To: "Kenneth Zadeck" <zadeck@naturalbridge.com>
Cc: "Revital1 Eres" <ERES@il.ibm.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	 	"Bonzini, Paolo" <bonzini@gnu.org>
Subject: Re: [patch]: To remove the Reaching Uses dataflow problem.
Date: Tue, 31 Jul 2007 16:26:00 -0000	[thread overview]
Message-ID: <ab3a61990707310900q64940394u9e93b2dbd4210dbf@mail.gmail.com> (raw)
In-Reply-To: <46AF57E6.90501@naturalbridge.com>

On 7/31/07, Kenneth Zadeck <zadeck@naturalbridge.com> wrote:
> Because of recent improvements to ddg.c, the reaching uses problem is no
> longer used.
> I am deleting it because it is not really a useful dataflow problem in
> that it tends to be more expensive to compute than reaching defs but
> provides little extra information.
>
> Removing the code will discourage any subsequent usage.
>
> I bootstrapped this change on x86-64.
>
> Ok for commit?
>
> Kenny
>
> 2007-07-31  Kenneth Zadeck <zadeck@naturalbridge.com>
>
>         * df.h (DF_RU, DF_RU_BB_INFO, df_ru_bb_info, df_ru,
>     df_ru_add_problem, df_ru_get_bb_info): Removed.
>     (DF_RD, DF_UREC, DF_CHAIN, DF_NOTE): Renumbered.
>     * df-problems.c (df_ru_problem_data, df_ru_set_bb_info,
>     df_ru_free_bb_info, df_ru_alloc,
>     df_ru_bb_local_compute_process_def,
>     df_ru_bb_local_compute_process_use, df_ru_bb_local_compute,
>     df_ru_local_compute, df_ru_init_solution, df_ru_confluence_n,
>     df_ru_transfer_function, df_ru_free, df_ru_start_dump,
>     df_ru_top_dump, df_ru_bottom_dump, df_problem problem_RU,
>     df_ru_add_problem): Removed.

Looks great to me.
-- 
#pragma ident "Seongbae Park, compiler, http://seongbae.blogspot.com"

  reply	other threads:[~2007-07-31 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 16:00 Kenneth Zadeck
2007-07-31 16:26 ` Seongbae Park (박성배, 朴成培) [this message]
2007-07-31 17:05   ` Kenneth Zadeck

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=ab3a61990707310900q64940394u9e93b2dbd4210dbf@mail.gmail.com \
    --to=seongbae.park@gmail.com \
    --cc=ERES@il.ibm.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=zadeck@naturalbridge.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).