From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <binutils-return-38390-listarch-binutils=sources.redhat.com@sources.redhat.com>
Received: (qmail 29837 invoked by alias); 1 Mar 2005 17:18:51 -0000
Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:binutils-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/binutils/>
List-Post: <mailto:binutils@sources.redhat.com>
List-Help: <mailto:binutils-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: binutils-owner@sources.redhat.com
Received: (qmail 29761 invoked from network); 1 Mar 2005 17:18:43 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sourceware.org with SMTP; 1 Mar 2005 17:18:43 -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 j21HIh3X002771
	for <binutils@sources.redhat.com>; Tue, 1 Mar 2005 12:18:43 -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 j21HIhK21559;
	Tue, 1 Mar 2005 12:18:43 -0500
Received: from [172.31.0.98] (vpnuser1.surrey.redhat.com [172.16.9.1])
	by pobox.surrey.redhat.com (8.12.8/8.12.8) with ESMTP id j21HIgZc024978;
	Tue, 1 Mar 2005 17:18:42 GMT
Message-ID: <4224A6A8.5010706@redhat.com>
Date: Tue, 01 Mar 2005 17:18:00 -0000
From: Nick Clifton <nickc@redhat.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
MIME-Version: 1.0
To: Hans-Peter Nilsson <hp@bitrange.com>
CC: binutils@sources.redhat.com
Subject: Re: Fix for unexpected failure in ld-cris/warn3
References: <m33bvfjptr.fsf@redhat.com> <Pine.BSF.4.58.0503011153590.23892@dair.pair.com>
In-Reply-To: <Pine.BSF.4.58.0503011153590.23892@dair.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2005-03/txt/msg00040.txt.bz2

Hi Hans-Peter,

> I don't see warnings in my regression tests.  Please specify.

Certainly.  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: <warning: isatty is not implemented and 
will always fail$>
   FAIL: ld-cris/warn3

> No, it seems to just paper over whatever problem there might be.
> The as and ld options should take care of the differences; both
> a.out and ELF formats are supported by both toolchains; defaults
> are different.
> 
> Please revert and elaborate.

OK - I have reverted my patch.

 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.

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

Cheers
   Nick