From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-86086-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 1388 invoked by alias); 20 Nov 2003 00:46:52 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 1381 invoked from network); 20 Nov 2003 00:46:51 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sources.redhat.com with SMTP; 20 Nov 2003 00:46:51 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id hAK0kfH18577;
	Wed, 19 Nov 2003 19:46:41 -0500
Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id hAK0kdw06636;
	Wed, 19 Nov 2003 19:46:39 -0500
Received: from dnovillo.cipe.redhat.com (dnovillo.cipe.redhat.com [10.0.0.106])
	by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id hAK0kYQ1006500;
	Wed, 19 Nov 2003 19:46:36 -0500
Subject: Re: Tree sharing issues...
From: Diego Novillo <dnovillo@redhat.com>
To: Jeff Law <law@redhat.com>
Cc: Jan Hubicka <jh@suse.cz>, Richard Henderson <rth@redhat.com>,
   Jan Hubicka <hubicka@ucw.cz>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
In-Reply-To: <200311200040.hAK0e5U5013862@speedy.slc.redhat.com>
References: <200311200040.hAK0e5U5013862@speedy.slc.redhat.com>
Content-Type: text/plain
Organization: Red Hat Canada
Message-Id: <1069289186.22708.10.camel@frodo.toronto.redhat.com>
Mime-Version: 1.0
Date: Thu, 20 Nov 2003 06:17:00 -0000
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-11/txt/msg01100.txt.bz2

On Wed, 2003-11-19 at 19:40, law@redhat.com wrote:
> In message <1069288378.22708.2.camel@frodo.toronto.redhat.com>, Diego Novillo w
> rites:
>  
>  >We always rewrite inside an ARRAY_REF.  Consider A[i][j].  Both i and j
>  >will be typically renamed.
> Err, what about when the index is a constant?
> 
Yeah, I had missed that.  In that case, sharing shouldn't be a problem
(like the example Jan posted earlier).  It goes back to following what
get_expr_operands does.  Any tree operand that may end up in def_ops or
use_ops must not be shared.


Diego.