From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5455 invoked by alias); 30 Oct 2002 20:36:01 -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 5424 invoked by uid 71); 30 Oct 2002 20:36:01 -0000 Date: Wed, 30 Oct 2002 12:36:00 -0000 Message-ID: <20021030203601.5417.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Nathanael Nerode Subject: Re: optimization/6162: gcc 3.0.4: certain i386 asm reloader ice Reply-To: Nathanael Nerode X-SW-Source: 2002-10/txt/msg01263.txt.bz2 List-Id: The following reply was made to PR optimization/6162; it has been noted by GNATS. From: Nathanael Nerode To: user42@zip.com.au, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc@gcc.gnu.org Cc: Subject: Re: optimization/6162: gcc 3.0.4: certain i386 asm reloader ice Date: Wed, 30 Oct 2002 15:29:20 -0500 I know this is a regression, but: * it's a subtle and difficult bug in reload, which may take a long time and a lot of work to find * reload is intended to go away for 3.4 * it only occurs using inline assembly * it only occurs with --fomit-frame-pointer I don't think it's reasonable to hold up 3.2.1 or 3.3 for this bug. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6162