From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21388 invoked by alias); 31 Mar 2003 20:36:15 -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 21371 invoked by uid 48); 31 Mar 2003 20:36:15 -0000 Date: Mon, 31 Mar 2003 21:10:00 -0000 Message-ID: <20030331203615.21370.qmail@sources.redhat.com> To: cgd@broadcom.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, rsandifo@sources.redhat.com From: rsandifo@sources.redhat.com Reply-To: rsandifo@sources.redhat.com, cgd@broadcom.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, rsandifo@sources.redhat.com, gcc-gnats@gcc.gnu.org Subject: Re: optimization/9301: [regression] [mips-linux] gcc 3.2.1 SEGV in try_forward_edges X-SW-Source: 2003-03/txt/msg02147.txt.bz2 List-Id: Synopsis: [regression] [mips-linux] gcc 3.2.1 SEGV in try_forward_edges State-Changed-From-To: feedback->closed State-Changed-By: rsandifo State-Changed-When: Mon Mar 31 20:36:15 2003 State-Changed-Why: Yes, reverting the fix for 9493 does cause the bug to resurface. I've installed the test case as suggested. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9301