From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26529 invoked by alias); 25 Mar 2011 17:28:49 -0000 Received: (qmail 26515 invoked by uid 22791); 25 Mar 2011 17:28:47 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from kiruna.synopsys.com (HELO kiruna.synopsys.com) (198.182.44.80) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 25 Mar 2011 17:28:43 +0000 Received: from crone.synopsys.com (crone.synopsys.com [146.225.7.23]) by kiruna.synopsys.com (Postfix) with ESMTP id DA745F812; Fri, 25 Mar 2011 10:28:42 -0700 (PDT) Received: from godel.synopsys.com (localhost [127.0.0.1]) by crone.synopsys.com (8.9.1/8.9.1) with ESMTP id KAA10844; Fri, 25 Mar 2011 10:28:42 -0700 (PDT) Received: from godel.synopsys.com (localhost [127.0.0.1]) by godel.synopsys.com (8.13.1/8.12.3) with ESMTP id p2PHSgE5024613; Fri, 25 Mar 2011 10:28:42 -0700 Received: (from jbuck@localhost) by godel.synopsys.com (8.13.1/8.13.1/Submit) id p2PHSXr8024570; Fri, 25 Mar 2011 10:28:33 -0700 Date: Fri, 25 Mar 2011 17:37:00 -0000 From: Joe Buck To: Jakub Jelinek Cc: "gcc@gcc.gnu.org" Subject: Re: Second GCC 4.6.0 release candidate is now available Message-ID: <20110325172833.GR5293@synopsys.com> References: <20110314172228.GO30899@tyan-ft48-01.lab.bos.redhat.com> <20110321221214.GB11563@sunsite.ms.mff.cuni.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110321221214.GB11563@sunsite.ms.mff.cuni.cz> User-Agent: Mutt/1.4.1i Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2011-03/txt/msg00407.txt.bz2 On Mon, Mar 21, 2011 at 03:12:14PM -0700, Jakub Jelinek wrote: > A second GCC 4.6.0 release candidate is available at: > > ftp://gcc.gnu.org/pub/gcc/snapshots/4.6.0-RC-20110321/ > > Please test the tarballs and report any problems to Bugzilla. > CC me on the bugs if you believe they are regressions from > previous releases severe enough to block the 4.6.0 release. See http://gcc.gnu.org/ml/gcc-testresults/2011-03/msg02463.html . There's an ICE for gcc.c-torture/compile/limits-exprparen.c which might be an issue. I think that the others may be due to the ancient version of glibc on RHEL 4 systems, though I haven't confirmed this.