public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/40834] [4.5 Regression] Revision 149750 failed 483.xalancbmk in SPEC CPU 2006
Date: Fri, 24 Jul 2009 19:59:00 -0000	[thread overview]
Message-ID: <20090724195905.9799.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40834-682@http.gcc.gnu.org/bugzilla/>



------- Comment #14 from rguenth at gcc dot gnu dot org  2009-07-24 19:59 -------
Index: cp/cp-gimplify.c
===================================================================
--- cp/cp-gimplify.c    (revision 150041)
+++ cp/cp-gimplify.c    (working copy)
@@ -804,10 +804,14 @@ cp_genericize_r (tree *stmt_p, int *walk
        }
     }

-  else if (TREE_CODE (stmt) == BIND_EXPR)
+  else if (TREE_CODE (stmt) == BIND_EXPR
+          /* We walk this twice, once to keep track of the BIND_EXPR
+             stack and once to properly walk the BIND_EXPR vars.  */
+          && (VEC_empty (tree, wtd->bind_expr_stack)
+              || VEC_last (tree, wtd->bind_expr_stack) != stmt))
     {
       VEC_safe_push (tree, heap, wtd->bind_expr_stack, stmt);
-      cp_walk_tree (&BIND_EXPR_BODY (stmt),
+      cp_walk_tree (stmt_p,
                    cp_genericize_r, data, NULL);
       VEC_pop (tree, wtd->bind_expr_stack);
       *walk_subtrees = 0;


in case you want to do some testing.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40834


  parent reply	other threads:[~2009-07-24 19:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  2:22 [Bug c++/40834] New: " hjl dot tools at gmail dot com
2009-07-23  8:47 ` [Bug c++/40834] " rguenth at gcc dot gnu dot org
2009-07-23 14:41 ` hjl dot tools at gmail dot com
2009-07-23 15:21 ` rguenther at suse dot de
2009-07-23 18:15 ` hjl dot tools at gmail dot com
2009-07-23 18:19 ` hjl dot tools at gmail dot com
2009-07-23 18:48 ` hjl dot tools at gmail dot com
2009-07-23 18:56 ` hjl dot tools at gmail dot com
2009-07-23 18:57 ` hjl dot tools at gmail dot com
2009-07-23 19:16 ` hjl dot tools at gmail dot com
2009-07-24  9:02 ` rguenther at suse dot de
2009-07-24 14:16 ` hjl dot tools at gmail dot com
2009-07-24 19:34 ` rguenth at gcc dot gnu dot org
2009-07-24 19:52 ` rguenth at gcc dot gnu dot org
2009-07-24 19:59 ` rguenth at gcc dot gnu dot org [this message]
2009-07-24 20:01 ` rguenth at gcc dot gnu dot org
2009-07-24 20:06 ` hjl dot tools at gmail dot com
2009-07-24 21:56 ` hjl dot tools at gmail dot com
2009-07-29 20:17 ` rguenth at gcc dot gnu dot org
2009-07-29 20:17 ` rguenth at gcc dot gnu dot org
2009-08-05 14:45 ` hjl at gcc dot gnu dot org

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=20090724195905.9799.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).