This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PR/6203 trunk patch, can it be moved to the 3.1 branch?
- From: Eric Christopher <echristo at redhat dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, "David dot Billinghurst at riotinto dot com" <David dot Billinghurst at riotinto dot com>, "aoliva at redhat dot com" <aoliva at redhat dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: 15 Apr 2002 11:01:43 -0700
- Subject: Re: PR/6203 trunk patch, can it be moved to the 3.1 branch?
- References: <200204092018.QAA25128@caip.rutgers.edu> <51690000.1018893090@gandalf.codesourcery.com>
> >
> > PR/6203 was fixed on the trunk by this patch:
> > http://gcc.gnu.org/ml/gcc-patches/2002-03/msg01087.html
>
> I'm sorry for the slow reply.
We're all busy :)
>
> > I'd like you to make a decision please as to whether this is safe
> > enough and/or appropriate for the 3.1 branch (or perhaps for 3.1.1).
>
> If it's a regression, it's OK for the branch, otherwise not.
>
It isn't technically a regression, the test is too new for it to be. I
do, however, believe it is important enough to go on the branch. This
fixes lots of failures with mips16 (things that may/may not be
regressions - mips16 has been broken since the mid 99) and fixes some
pretty bad register elimination problems.
-eric
--
Written using state-of-the-rat
technology.