public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH][mem-ref2] Revert expand_debug_expr change
Date: Fri, 25 Jun 2010 15:27:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1006251632400.1429@zhemvz.fhfr.qr> (raw)


This reverts the other odd change noticed.  This was probably
fixed by the inliner fixes.

Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.

Richard.

2010-06-25  Richard Guenther  <rguenther@suse.de>

	* cfgexpand.c (expand_debug_expr): Revert change.

Index: gcc/cfgexpand.c
===================================================================
--- gcc/cfgexpand.c	(revision 161369)
+++ gcc/cfgexpand.c	(working copy)
@@ -2504,31 +2504,10 @@ expand_debug_expr (tree exp)
 	HOST_WIDE_INT bitsize, bitpos;
 	tree offset;
 	int volatilep = 0;
-	tree *tp = &exp;
-	tree tem;
+	tree tem = get_inner_reference (exp, &bitsize, &bitpos, &offset,
+					&mode1, &unsignedp, &volatilep, false);
 	rtx orig_op0;
 
-	/* First fold un-folded results from CCP.  */
-	do
-	  {
-	    while (handled_component_p (*tp))
-	      tp = &TREE_OPERAND (*tp, 0);
-	    if (TREE_CODE (*tp) == MEM_REF)
-	      {
-		tem = fold_binary (MEM_REF, TREE_TYPE (*tp),
-				   TREE_OPERAND (*tp, 0),
-				   TREE_OPERAND (*tp, 1));
-		if (!tem)
-		  break;
-		*tp = tem;
-	      }
-	    else
-	      break;
-	  }
-	while (1);
-
-	tem = get_inner_reference (exp, &bitsize, &bitpos, &offset,
-				   &mode1, &unsignedp, &volatilep, false);
 	if (bitsize == 0)
 	  return NULL;
 

                 reply	other threads:[~2010-06-25 14:33 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=alpine.LNX.2.00.1006251632400.1429@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --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).