From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2424 invoked by alias); 15 Mar 2006 04:38:02 -0000 Received: (qmail 2416 invoked by uid 22791); 15 Mar 2006 04:38:02 -0000 X-Spam-Check-By: sourceware.org Received: from eyesopen.com (HELO www.eyesopen.com) (208.41.78.163) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 15 Mar 2006 04:37:59 +0000 Received: from localhost (roger@localhost) by www.eyesopen.com (8.11.6/8.11.6) with ESMTP id k2F4J9813310; Tue, 14 Mar 2006 21:19:10 -0700 Date: Wed, 15 Mar 2006 04:38:00 -0000 From: Roger Sayle To: Steve Ellcey cc: gcc-patches@gcc.gnu.org, Subject: Re: Patch ping In-Reply-To: <200603141649.IAA14478@hpsje.cup.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2006-03/txt/msg00900.txt.bz2 On Tue, 14 Mar 2006, Steve Ellcey wrote: > > 2006-03-13 Uttam Pawar > > > > * gensupport.c (identify_predicable_attribute): Free > > p_false pointer. > > * gcov.c (create_file_names): Free name pointer. > > > > PR rtl-optimization/25739 > > * bt-load.c (augment_live_range): Free tos pointer. > > I think that this patch may be breaking the IA64 bootstrap (HP-UX and > Linux). It is dying with: > > build/genmddeps /proj/opensrc/nightly/src/trunk/gcc/config/ia64/ia64.md > tmp-mddeps > /proj/opensrc/nightly/src/trunk/gcc/config/ia64/ia64.md:792: unknown value `no' for `predicable' attribute > /proj/opensrc/nightly/src/trunk/gcc/config/ia64/ia64.md:1992: unknown value `no' for `predicable' attribute > > (and a bunch more) > > I am guessing this may be related to the change made to > identify_predicable_attribute. Is anyone seeing this? Grrr! I was most of the way through an IA-64 bootstrap of a fix (along the lines of Andrew Pinski's suggestion), when someone at OpenEye decided to switch off the SGI Altix box I was using (as the air conditioning in the machine room just gave up). I suspect (hope?) that someone will post/commit a fix soon, but if not I'll get back to it once my Itanium boxes are back online. Roger --