From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21697 invoked by alias); 2 May 2003 13:15:22 -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 21677 invoked by uid 48); 2 May 2003 13:15:22 -0000 Date: Fri, 02 May 2003 13:15:00 -0000 Message-ID: <20030502131522.21676.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, ryan.pipkin@inet.com From: rearnsha@gcc.gnu.org Reply-To: rearnsha@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, ryan.pipkin@inet.com, gcc-gnats@gcc.gnu.org Subject: Re: optimization/10592: [arm] caller-save incorrectly handles a reloaded SET_DEST operand X-SW-Source: 2003-05/txt/msg00127.txt.bz2 List-Id: Old Synopsis: apcs frame causing register mishandling New Synopsis: [arm] caller-save incorrectly handles a reloaded SET_DEST operand State-Changed-From-To: open->analyzed State-Changed-By: rearnsha State-Changed-When: Fri May 2 13:15:22 2003 State-Changed-Why: This is a bug in the caller-save code. You can work around it for now by using -fno-caller-saves. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10592