From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17968 invoked by alias); 31 Jan 2003 20:42:58 -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 17947 invoked by uid 48); 31 Jan 2003 20:42:58 -0000 Date: Fri, 31 Jan 2003 20:42:00 -0000 Message-ID: <20030131204258.17946.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, maddinp@yahoo.de, nobody@gcc.gnu.org From: bangerth@dealii.org Reply-To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, maddinp@yahoo.de, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: optimization/9426: [3.2 regression] SegFault during optimization X-SW-Source: 2003-01/txt/msg01794.txt.bz2 List-Id: Old Synopsis: gcc 3.2.1 crash during optimization New Synopsis: [3.2 regression] SegFault during optimization State-Changed-From-To: feedback->analyzed State-Changed-By: bangerth State-Changed-When: Fri Jan 31 20:42:58 2003 State-Changed-Why: I can reproduce this with the little testcase that is given in the feedback mail. Note that one needs to add either -march=i486 or i586 to the command line, the problem doesn't happen with i686 (which is the default for me, which is why I didn't see the ICE at first). The bug is fixed with present 3.3 and 3.4 CVS, but since this worked in 3.0.4, I keep the report open as a regression as long as the 3.2 branch is still maintained. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9426