This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: New ld failure with STB_GNU_UNIQUE patch
- From: "Maciej W. Rozycki" <macro at imgtec dot com>
- To: Nick Clifton <nickc at redhat dot com>
- Cc: <binutils at sourceware dot org>
- Date: Tue, 17 May 2016 17:31:13 +0100
- Subject: Re: New ld failure with STB_GNU_UNIQUE patch
- Authentication-results: sourceware.org; auth=none
- References: <8760ucpz4e dot fsf at redhat dot com> <alpine dot DEB dot 2 dot 00 dot 1605171514420 dot 6794 at tp dot orcam dot me dot uk>
On Tue, 17 May 2016, Maciej W. Rozycki wrote:
> > I have encountered a new failure in the LD tests for the ft32-elf
> > target:
> >
> > Executing on host: sh -c {./ld-new -L/work/sources/binutils/current/ld/testsuite/ld-unique -r -o tmpdir/dump tmpdir/dump0.o 2>&1} /dev/null ld.tmp (timeout = 300)
> > spawn [open ...]
> > ./ld-new: invalid length for memory region flash
> > failed with: <./ld-new: invalid length for memory region flash>, no expected output
> > ./ld-new: invalid length for memory region flash
> > FAIL: Linker setting GNU OSABI on STB_GNU_UNIQUE symbol (PR 10549)
> >
> > Would you mind having a look at this please ?
>
> Sure, I'll add `ft32-elf' to my regular testing for generic changes too.
So it's just that on `ft32-elf' all tests that call LD with no substitute
linker script supplied fail with this error, unless they hit `-shared not
supported' first. I think this means that the default linker script is
broken, and this newly-enabled test just follows the pattern. Does this
observation address your concern?
I can't offer my time right now to fix the `ft32-elf' target I'm afraid,
sorry.
Maciej