From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18367 invoked by alias); 16 Dec 2002 09:08:06 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 18358 invoked from network); 16 Dec 2002 09:08:04 -0000 Received: from unknown (HELO nikam.ms.mff.cuni.cz) (195.113.18.106) by sources.redhat.com with SMTP; 16 Dec 2002 09:08:04 -0000 Received: by nikam.ms.mff.cuni.cz (Postfix, from userid 16202) id 2B6924DED8; Mon, 16 Dec 2002 10:08:04 +0100 (CET) Date: Mon, 16 Dec 2002 01:46:00 -0000 From: Jan Hubicka To: Zack Weinberg Cc: gcc@gcc.gnu.org Subject: Re: basic-improvements merge status Message-ID: <20021216090804.GE3824@kam.mff.cuni.cz> References: <87u1hex3o9.fsf@egil.codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87u1hex3o9.fsf@egil.codesourcery.com> User-Agent: Mutt/1.3.28i X-SW-Source: 2002-12/txt/msg00864.txt.bz2 > > Since my last posting on the subject, the Makefile and 32x64 issues > have been resolved and patches checked in. I have also read through > the entire diff between 3.3 branchpoint and 3.4bib top of branch, to > make sure that no patches have gotten lost. (It's possible that I > missed something.) > > Still unresolved problems reported to me are: > > - hppa weak symbols problem > - hppa g++ testsuite failures apparently to do with structure return > - darwin stubs problem > - darwin bootstrap failure > - irix6.5 bootstrap failure > - cygwin bootstrap failure > > I do not have access to the systems involved, or enough knowledge of > them to fix the problems even if I did. I need help from people who > have both these things. > > It is not clear to me that any purpose is served by holding off the > merge to trunk until all these issues get resolved. We could instead > do the merge now and fix the problems on the mainline; this would let > people move forward with other work. It would probably be a good idea > in that case to hold off on further branch merges and other massively > destabilizing patches until these issues do get resolved. > > Thoughts? I perfectly aggree. All these are mostly configuration problems and can be fixed once merge is done. It looks like branch bootstrap en enought different CPUs when configured properly giving enought evidence that it is not broken by design. Merging and reopening mainline will let other work to be integrated... Also you may check http://www.suse.de/~aj/SPEC for benchmarks from last week. Fortunately there seems to be no important regressions relative to mainline and some important speedups. Honza > > zw