From d8f4ff4b57ef3f6b3bf65bdae6c394155769145b Mon Sep 17 00:00:00 2001
From: Stephen Williams <steve@icarus.com>
Date: Fri, 9 Aug 2013 20:55:18 -0700
Subject: [PATCH] Remove eval_expr during PEBinary elaboration

Turns out that call to eval_expr is redundant, and in degenerate
situations can lead to so many wasteful calls to eval_expr that
elaboration performance suffers dramatically.
---
 elab_expr.cc | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/elab_expr.cc b/elab_expr.cc
index 544bd55f7..233f72c00 100644
--- a/elab_expr.cc
+++ b/elab_expr.cc
@@ -285,11 +285,6 @@ NetExpr* PEBinary::elaborate_expr(Design*des, NetScope*scope,
 	    return 0;
       }
 
-	// If either expression can be evaluated ahead of time, then
-	// do so. This can prove helpful later.
-      eval_expr(lp, l_width);
-      eval_expr(rp, r_width);
-
       return elaborate_expr_base_(des, lp, rp, expr_wid);
 }