From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27813 invoked by alias); 28 Jun 2005 15:51: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 27636 invoked by uid 22791); 28 Jun 2005 15:51:02 -0000 Received: from dumbledore.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.11) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 28 Jun 2005 15:51:02 +0000 Received: (qmail 4145 invoked from network); 28 Jun 2005 15:51:00 -0000 Received: from unknown (HELO ?192.168.0.4?) (mitchell@127.0.0.2) by mail.codesourcery.com with ESMTPA; 28 Jun 2005 15:51:00 -0000 Message-ID: <42C171DD.4090408@codesourcery.com> Date: Tue, 28 Jun 2005 15:51:00 -0000 From: Mark Mitchell User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: law@redhat.com CC: gcc mailing list Subject: Re: GCC 4.0.1 Status (2005-06-27) References: <42C0FA31.9000307@codesourcery.com> <1119973190.4621.79.camel@localhost.localdomain> In-Reply-To: <1119973190.4621.79.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-06/txt/msg01131.txt.bz2 Jeffrey A Law wrote: > On Tue, 2005-06-28 at 00:20 -0700, Mark Mitchell wrote: > >>As stated earlier, the only patches I'm considering for 4.0.1 at present >>are wrong-code cases on primary platforms. There are several open, but >>the only one I consider a show-stopper is PR 22051, which Jeff Law is >>working on, and hopes to fix Tuesday. As soon as that's in, I'll build >>RC3, and then, hopefully, a few days later, put out the final release. >> >>I'm sorry this is dragging out, but I think it's worth getting this bug >>fixed. > > I'm working on it right now. My PA box is experiencing cpu faults > on its second cpu while trying to bootstrap for a set of baseline > results.... I suspect it'll take until late tomorrow before I can get > a set of baseline test results, fix the bug, then get a set of new test > results for comparison purposes. Perhaps you could get a patch put together, test it by staring atassembly output, and then ask for a volunteer to test it? I expect that Joseph could do a test run on PA-HPUX for you. -- Mark Mitchell CodeSourcery, LLC mark@codesourcery.com (916) 791-8304