public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com>
To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Patches ping
Date: Tue, 10 May 2005 16:49:00 -0000	[thread overview]
Message-ID: <20050510164906.GA7455@topo.toronto.redhat.com> (raw)
In-Reply-To: <20050506210933.GA21336@atrey.karlin.mff.cuni.cz>

On Fri, May 06, 2005 at 11:09:33PM +0200, Zdenek Dvorak wrote:

> 	* tree-ssa-loop-im.c: Include hashtab.h.
> 	(struct mem_ref_loc): New.
> 	(struct mem_ref): Describe the set of references with the same
> 	shape.
> 	(max_stmt_uid, get_stmt_uid, record_mem_ref, free_mem_refs,
> 	maybe_queue_var, fem_single_reachable_address,
> 	for_each_memref, single_reachable_address,
> 	is_call_clobbered_ref, determine_lsm_reg): Removed.
> 	(record_mem_ref_loc, free_mem_ref_locs, determine_lsm_ref,
> 	hoist_memory_reference, memref_hash, memref_eq, memref_del,
> 	gather_mem_refs_stmt, gather_mem_refs, find_more_ref_vops):
> 	New functions.
> 	(rewrite_mem_refs, schedule_sm): Use mem_ref_loc list.
> 	(determine_lsm_loop): Rewritten.
> 	(determine_lsm): Do not set stmt uids.
> 
This version is much easier to follow than the original.  Thanks.
The patch is fine.  A couple of minor comment fixes:

> + 
> +   /* If we cannot create a ssa name for the result, give up.  */
                             ^^^^^
			     an SSA

> +   if (!is_gimple_reg_type (TREE_TYPE (*mem))
> +       || TREE_THIS_VOLATILE (*mem))
> +     goto fail;
> + 
> +   /* If we cannot move the reference from the loop, fail.  */
                                         ^^^^
					 out of


Diego.

  reply	other threads:[~2005-05-10 16:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 11:38 Zdenek Dvorak
2005-05-04 12:48 ` Andrew MacLeod
2005-05-04 18:21   ` Andrew MacLeod
2005-05-04 18:44     ` Zdenek Dvorak
2005-05-04 19:23       ` Devang Patel
2005-05-04 20:26         ` Andrew MacLeod
2005-05-04 20:39           ` Zdenek Dvorak
2005-05-04 21:03           ` Devang Patel
2005-05-04 21:07             ` Zdenek Dvorak
2005-05-04 21:19               ` Devang Patel
2005-05-04 21:56                 ` Zdenek Dvorak
2005-05-05  6:27       ` Dorit Naishlos
2005-05-04 13:25 ` Diego Novillo
2005-05-06 21:09   ` Zdenek Dvorak
2005-05-10 16:49     ` Diego Novillo [this message]
2005-05-16  3:55 ` Geoffrey Keating
  -- strict thread matches above, loose matches on Subject: below --
2011-12-27  9:43 Revital Eres
2011-07-20  8:35 Revital Eres
2011-07-29 21:47 ` Ayal Zaks
2011-08-01  8:41   ` Revital1 Eres
2011-07-29 21:48 ` Ayal Zaks
2011-07-29 22:15 ` Ayal Zaks
2011-05-26  9:14 Revital Eres
2011-04-27  5:22 Revital Eres
2005-03-25  8:35 Alexey Neyman
2005-03-18  8:50 Alexey Neyman
2005-03-18 11:08 ` Paolo Bonzini
2005-03-12  7:02 Alexey Neyman
2005-03-08  8:17 Alexey Neyman
2004-12-20 11:13 Alexey Neyman
2004-12-25 14:34 ` Gerald Pfeifer
2004-11-28  0:55 H. J. Lu
2004-10-08 21:38 Zdenek Dvorak

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=20050510164906.GA7455@topo.toronto.redhat.com \
    --to=dnovillo@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rakdver@atrey.karlin.mff.cuni.cz \
    /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).