This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] tree-ssa-dom.c: Use VEC(vrp_element_p,heap) instead ofVARRAY.

From: Jeffrey A Law <law at redhat dot com>
To: Diego Novillo <dnovillo at redhat dot com>
Cc: Kazu Hirata <kazu at cs dot umass dot edu>, gcc-patches at gcc dot gnu dot org, nathan at codesourcery dot com
Date: Wed, 27 Apr 2005 11:13:25 -0600
Subject: Re: [patch] tree-ssa-dom.c: Use VEC(vrp_element_p,heap) instead ofVARRAY.
Organization: Red Hat, Inc
References: <20050427.093812.78159407.kazu@cs.umass.edu> <1114609621.370.1.camel@localhost.localdomain> <20050427.121951.85389895.kazu@cs.umass.edu> <20050427170157.GA27784@topo.toronto.redhat.com>
Reply-to: law at redhat dot com

On Wed, 2005-04-27 at 13:01 -0400, Diego Novillo wrote:
> On Wed, Apr 27, 2005 at 12:19:51PM -0400, Kazu Hirata wrote:
> 
> > Well, we can probably feed DOM similar information using
> > SSA_NAME_VALUE_RANGE.
> > 
> If DOM doesn't use the VRP info for jump threading,
It will try to use DOM's VRP for jump threading.  However, I suspect
it is the case that VRP information is typically not the deciding
factor whether or not to thread a jump.  It wouldn't be terribly
hard to instrument DOM to tells us how often it threads a jump using
VRP information.

Jeff

References:
- [patch] tree-ssa-dom.c: Use VEC(vrp_element_p,heap) instead ofVARRAY.
  - From: Kazu Hirata
- Re: [patch] tree-ssa-dom.c: Use VEC(vrp_element_p,heap) instead ofVARRAY.
  - From: Jeffrey A Law
- Re: [patch] tree-ssa-dom.c: Use VEC(vrp_element_p,heap) instead ofVARRAY.
  - From: Kazu Hirata
- Re: [patch] tree-ssa-dom.c: Use VEC(vrp_element_p,heap) instead of VARRAY.
  - From: Diego Novillo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]