public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bin Cheng" <bin.cheng@arm.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [PATCH GCC][obvious]Don't reset ssa_name infor in struct iv.
Date: Fri, 26 Jun 2015 08:49:00 -0000	[thread overview]
Message-ID: <000401d0afec$e951f6f0$bbf5e4d0$@arm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 295 bytes --]

Hi,
I applied a patch before to keep ssa_name information in struct iv.  Seems
this function somehow slipped away.
Will apply it to trunk.

Thanks,
bin

2015-06-26  Bin Cheng  <bin.cheng@arm.com>

	* tree-ssa-loop-ivopts.c (record_sub_use): Don't reset ssa_name
	field in struct iv.

[-- Attachment #2: keep-ssa_name-in-iv.txt --]
[-- Type: text/plain, Size: 461 bytes --]

Index: gcc/tree-ssa-loop-ivopts.c
===================================================================
--- gcc/tree-ssa-loop-ivopts.c	(revision 224930)
+++ gcc/tree-ssa-loop-ivopts.c	(working copy)
@@ -1390,10 +1396,6 @@ record_sub_use (struct ivopts_data *data, tree *us
       pre->next = use;
     }
 
-  /* To avoid showing ssa name in the dumps, if it was not reset by the
-     caller.  */
-  iv->ssa_name = NULL_TREE;
-
   return use;
 }
 

                 reply	other threads:[~2015-06-26  8:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='000401d0afec$e951f6f0$bbf5e4d0$@arm.com' \
    --to=bin.cheng@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).