From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9987 invoked by alias); 13 Dec 2002 18:06:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 9971 invoked by uid 71); 13 Dec 2002 18:06:02 -0000 Date: Fri, 13 Dec 2002 10:06:00 -0000 Message-ID: <20021213180602.9970.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Eric Botcazou Subject: Re: optimization/7799: [3.2/3.3 regression] Loop bug with optimization flag -Os in gcc Reply-To: Eric Botcazou X-SW-Source: 2002-12/txt/msg00766.txt.bz2 List-Id: The following reply was made to PR optimization/7799; it has been noted by GNATS. From: Eric Botcazou To: "Christian Ehrhardt" Cc: nejataydin@superonline.com, gcc-gnats@gcc.gnu.org, gcc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: optimization/7799: [3.2/3.3 regression] Loop bug with optimization flag -Os in gcc Date: Fri, 13 Dec 2002 18:51:12 +0100 > Thanks for the clarification. This means that we can close the report? 'Suspended' is probably better. > I can confirm that using -fno-strength-reduce fixes the problem. The culprit is actually not the strength reduction pass per se, but the=20 induction variable elimination pass that is bundled with it. --=20 Eric Botcazou