From mboxrd@z Thu Jan  1 00:00:00 1970
From: rth@gcc.gnu.org
To: denisc@overta.ru, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, rth@gcc.gnu.org
Subject: Re: target/3037: ARM port: Wrong flow info after reload
Date: Mon, 11 Jun 2001 14:34:00 -0000
Message-id: <20010611213436.5043.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-06/msg00439.html
List-Id: <gcc-prs.sourceware.org>

Synopsis: ARM port: Wrong flow info after reload

State-Changed-From-To: open->feedback
State-Changed-By: rth
State-Changed-When: Mon Jun 11 14:34:36 2001
State-Changed-Why:
    Err, ok, yes, the interaction between the arm backend and flow
    keeps registers live when they oughtn't be.  That seems rather
    minor though.  Why is this pr marked "critical"?  I'm presuming
    based on "ice-on-legal-code" that this test case was supposed 
    to segfault or something, but as you didn't give compilation 
    flags I was forced to guess, and didn't come up with a
    combination that dies.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3037&database=gcc