From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7819 invoked by alias); 16 Oct 2002 14:53:04 -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 7703 invoked from network); 16 Oct 2002 14:53:00 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (66.187.233.200) by sources.redhat.com with SMTP; 16 Oct 2002 14:53:00 -0000 Received: from scox.rdu.redhat.com (dhcp59-238.rdu.redhat.com [172.16.59.238]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id g9GEqtP03570; Wed, 16 Oct 2002 10:52:55 -0400 Received: (from scox@localhost) by scox.rdu.redhat.com (8.11.0/8.11.0) id g9GEtq701173; Wed, 16 Oct 2002 10:55:52 -0400 Date: Wed, 16 Oct 2002 09:43:00 -0000 From: scox@redhat.com Message-Id: <200210161455.g9GEtq701173@scox.rdu.redhat.com> To: aj@suse.de, ritu@csa.iisc.ernet.in Subject: Re: Loop dependence analysis!! Cc: gcc@gcc.gnu.org, scox@redhat.com X-SW-Source: 2002-10/txt/msg00957.txt.bz2 > Or will the rest get added at some point? The front end didn't have the infrastructure to recognize and analyze loops, so it was easier to wait until that was available. Now that it is becoming available it will be possible to hook that in and make it useful. It pretty much implements the GCD test.