Re: Fix for unexpected failure in ld-cris/warn3

[Nick Clifton <nickc at redhat dot com>]

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