From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18844 invoked by alias); 8 Mar 2005 15:00:58 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 18798 invoked from network); 8 Mar 2005 15:00:54 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 8 Mar 2005 15:00:54 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j28F0sk6008753 for ; Tue, 8 Mar 2005 10:00:54 -0500 Received: from pobox.surrey.redhat.com (pobox.surrey.redhat.com [172.16.10.17]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j28F0rn12306; Tue, 8 Mar 2005 10:00:53 -0500 Received: from [172.31.0.98] (vpnuser4.surrey.redhat.com [172.16.9.4]) by pobox.surrey.redhat.com (8.12.8/8.12.8) with ESMTP id j28F0ppa013124; Tue, 8 Mar 2005 15:00:52 GMT Message-ID: <422DC0F5.6060703@redhat.com> Date: Tue, 08 Mar 2005 15:00:00 -0000 From: Nick Clifton User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) MIME-Version: 1.0 To: Hans-Peter Nilsson CC: binutils@sources.redhat.com Subject: Re: Fix for unexpected failure in ld-cris/warn3 References: <4224A6A8.5010706@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-03/txt/msg00219.txt.bz2 Hi Hans-Peter, > I tried to repeat this but still do not see the failure on > x86_64-unknown-linux-gnu (RH Ent AS 3.0, > spe189.testdrive.hp.com). Strange... I am running pretty the same environment on my host: Linux workshop 2.4.21-27.0.2.EL #1 Wed Jan 12 23:35:46 EST 2005 i686 athlon i386 GNU/Linux > No failures in the ld-cris/cris.exp > section. I do see failures that look like 32/64-bit issues in > the gas testsuite FWIW. > > I'm suspecting local patches in your tree (completely without > cause). Actually with good cause - I do have several of those, but I have just backed them out, reconfigured and rebuilt a cris-elf toolchain from scratch and the failure still happens... > I don't know how to proceed here except to leave it, as it works > for me. Can you repeat the test? Yes and the failure is still there. It occurred to me that the discrepancy might be due to the fact that I am using a different version of gcc. I am using the GNUPro version that RedHat ships to various paying customers which is based on gcc 3.4 rather than the gcc 3.2.3 version which is the system default for RHEL3. Unfortunately I tried reverting to the system compiler and the failure still happened. Where is the stabs warning message generated anyway ? ie which functions in bfd and/or ld are responsible for detecting the stab message and printing it out ? Cheers Nick