This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: trunk still frozen?
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Jason R Thorpe <thorpej at wasabisystems dot com>
- Cc: Richard dot Earnshaw at arm dot com, Mark Mitchell <mark at codesourcery dot com>, "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, "zack at codesourcery dot com" <zack at codesourcery dot com>
- Date: Thu, 19 Dec 2002 10:25:59 +0000
- Subject: Re: trunk still frozen?
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> On Wed, Dec 18, 2002 at 10:51:49AM +0000, Richard Earnshaw wrote:
>
> > arm-netbsdelf is bootstrapping ok, but showing many new regressions from
> > the testsuite. I haven't had chance to investigate why yet, but most of
> > them seem to be c++ related (it wouldn't surprise me if this is a sj/lj
> > exception regression).
>
> Some of these may be related to the USER_H change I made to the netbsd
> configs; as Krister pointed out, I didn't test that change in as many
> environments as I should have (sigh). I'm going to try and deal with
> that today/tonight (on the trunk and 3.3 branch), but I was delayed by
> losing a processor board on the AlphaServer that holds my source trees.
I doubt it. Firstly, these are execute failures -- if it were the headers
then I'd expect them to be compile failures. Secondly, I get exactly the
same g++ failures on an arm-elf cross (For some reason the libstdc++-v3
tests still don't run in a multilib build).
I'll file the PR as Mark requested, but I won't be around after today to
look into this until the New Year.
R.