From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Nick Clifton <nickc@redhat.com>
Cc: <binutils@sourceware.org>
Subject: Re: New ld failure with STB_GNU_UNIQUE patch
Date: Tue, 17 May 2016 16:31:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1605171719070.6794@tp.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1605171514420.6794@tp.orcam.me.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
next prev parent reply other threads:[~2016-05-17 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 13:56 Nick Clifton
2016-05-17 14:17 ` Maciej W. Rozycki
2016-05-17 16:31 ` Maciej W. Rozycki [this message]
2016-05-18 9:11 ` Nick Clifton
2016-05-18 9:16 ` Maciej W. Rozycki
2016-05-18 9:55 ` Nick Clifton
2016-05-19 10:23 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1605171719070.6794@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).