This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/3037: ARM port: Wrong flow info after reload
- To: denisc at overta dot ru, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, rth at gcc dot gnu dot org
- Subject: Re: target/3037: ARM port: Wrong flow info after reload
- From: rth at gcc dot gnu dot org
- Date: 11 Jun 2001 21:34:36 -0000
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