This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.1 Issues
- From: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: 15 Mar 2002 00:52:46 +0100
- Subject: Re: GCC 3.1 Issues
- References: <45810000.1015438826@gandalf.codesourcery.com>
Mark Mitchell <mark@codesourcery.com> writes:
> If you know of regressions in GCC 3.1 relative to previous releases,
> or major issues that stand between us and a GCC 3.0 release, please
> file PRs in GNATS and send the PR numbers to me.
* PR libgcj/5944: libgcj fails to bootstrap on alpha-dec-osf4.0f and
sparc-sun-solaris2.5.1, a regression from 3.0.5
* PR target/5949: GCJ gets an ICE bootstrapping libgcj on alpha-dec-osf5.1,
a regression from 3.0.5
* PR bootstrap/5948: bootstrap failure on i386-pc-solaris2.8, a regression
from 3.0.5
* PR target/5966: many EH failures on alpha-dec-osf5.1, a regression from
3.0.5
Btw., who may mark those PRs high priority: anyone with GNATS write access
or only global write privs or other maintainers?
Besides, I've started bootstrapping from the tops of the 3.0 and 3.1
branches on various platforms
http://gcc.gnu.org/ml/java/2002-03/msg00289.html
and started investigating testsuite failures. How should I best handle
those that I can analyse? File individual PRs for the various failure
modes found?
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University