From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11198 invoked by alias); 1 Mar 2005 17:34:35 -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 11148 invoked from network); 1 Mar 2005 17:34:27 -0000 Received: from unknown (HELO dair.pair.com) (209.68.1.49) by sourceware.org with SMTP; 1 Mar 2005 17:34:27 -0000 Received: (qmail 56127 invoked by uid 20157); 1 Mar 2005 17:34:26 -0000 Date: Tue, 01 Mar 2005 17:34:00 -0000 From: Hans-Peter Nilsson X-X-Sender: hp@dair.pair.com To: Nick Clifton cc: binutils@sources.redhat.com Subject: Re: Fix for unexpected failure in ld-cris/warn3 In-Reply-To: <4224A6A8.5010706@redhat.com> Message-ID: References: <4224A6A8.5010706@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2005-03/txt/msg00042.txt.bz2 Hi Nick On Tue, 1 Mar 2005, Nick Clifton wrote: > With a toolchain configured as --target=cris-elf and built > on an x86_64 host running Linux I saw these messages in the ld.log when > running the linker tests: > > succeeded with: <>, expected: will always fail$> > FAIL: ld-cris/warn3 Thanks. I have not seen this in autotester runs on i686-pc-linux-gnu cross to cris-axis-elf. Maybe it's a 64-bit-host thingy; the test for the warning failing there. I'll try and get hold of one and test there. > From looking at the warn3.d and warn4.d files I had thought that one > was intended to be run for the cris-elf target and another for the > cris-aout target. Obviously I was wrong. They're indeed meant for a.out and ELF, but as the assembler and linker support both formats, both tests run on both cris-*-elf and cris-*-aout. Maybe a bit confusing if you're not used to GAS being multiformat. :-) > Incidentally I do not normally test the cris-aout target but whilst > investigating this problem I thought that it would be a good idea to > check. It seems to generate quite a lot of unexpected failures in the > linker's ld-cris testsuite, most of which are due to this error message: > > Error: --no-underscore is invalid with a.out format Thanks. I do not normally test cris-aout but will do so and fix stragglers. brgds, H-P