From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11444 invoked by alias); 13 Dec 2002 05:06:27 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 11385 invoked from network); 13 Dec 2002 05:06:19 -0000 Received: from unknown (HELO ngate.noida.hcltech.com) (202.54.110.230) by sources.redhat.com with SMTP; 13 Dec 2002 05:06:19 -0000 Received: from exch-01.noida.hcltech.com (exch-01 [204.160.254.29]) by ngate.noida.hcltech.com (8.9.3/8.9.3) with ESMTP id KAA31739; Fri, 13 Dec 2002 10:33:41 +0530 Received: by exch-01.noida.hcltech.com with Internet Mail Service (5.5.2653.19) id ; Fri, 13 Dec 2002 10:30:44 +0530 Message-ID: From: "Sanjiv Kumar Gupta, Noida" To: Geoff Keating , Richard Henderson Cc: Daniel Berlin , Dale Johannesen , gcc@gcc.gnu.org Subject: RE: possible gcse failure: not able to eliminate redundant loads Date: Thu, 12 Dec 2002 21:35:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2002-12/txt/msg00702.txt.bz2 >> We have the code for it, but alias.c isn't helping. >It looks like memrefs_conflict_p is supposed to be able to prove that a[2] and a[4] don't alias, I wonder why it's not working? It can detect different offsets in 'reg+offset' forms of addresses but can not distinguish between two pointer regs. In this case, the machine (sh4) doesn't support reg+offset addressing for double-precision values. I am working on memrefs_conflict_p to handle this. --Sanjiv