From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26765 invoked by alias); 23 Apr 2009 06:04:01 -0000 Received: (qmail 26696 invoked by uid 48); 23 Apr 2009 06:03:50 -0000 Date: Thu, 23 Apr 2009 06:04:00 -0000 Message-ID: <20090423060350.26695.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jakub at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-04/txt/msg02099.txt.bz2 ------- Comment #5 from jakub at gcc dot gnu dot org 2009-04-23 06:03 ------- GCC 4.4.0 compiled glibc 2.10 works just fine for me on x86_64, i586, i686, powerpc and powerpc64. Anyway, if you say GCC 4.3.3 compiled glibc 2.8 works and 4.4.0 compiled doesn't, then please do a binary search between 4.3.3 and 4.4.0 compiled objects to find out on which CU it matters (say configure glibc with CC=gcc CXX=g++, then point PATH env var. to wher eyou have gcc 4.4.0 unpacked, build glibc, verify your testcase breaks, then in the build tree for i in [a-l]*/*.os; do mv ${i}{,.4.4}; done change PATH to point to 4.3.3 gcc, make, see whether your testcase breaks or not and depending on that continue with either half of the [a-l]* or [m-z]* objects, etc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39852