From: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
To: Nick Clifton <nickc@redhat.com>,
"John.Martin@emmicro-us.com" <John.Martin@emmicro-us.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: New ARC linker testsuite failure
Date: Thu, 20 Jul 2017 10:12:00 -0000 [thread overview]
Message-ID: <098ECE41A0A6114BB2A07F1EC238DE89666309AB@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <87379sleq2.fsf@redhat.com>
Sure, sorry for this.
Claudiu
> -----Original Message-----
> From: Nick Clifton [mailto:nickc@redhat.com]
> Sent: Wednesday, July 19, 2017 3:49 PM
> To: Claudiu.Zissulescu@synopsys.com; John.Martin@emmicro-us.com
> Cc: binutils@sourceware.org
> Subject: New ARC linker testsuite failure
>
> Hi Claudiu, Hi John,
>
> A new linker testsuite failure has just shown up:
>
> FAIL: ld-arc/jli-overflow
>
> This is only with the arceb-elf target and the log file appears to
> suggest that you need to add an endian specifier when linking:
>
> ./ld-new: tmpdir/jli-overflow.o: compiled for a big endian system and target
> is little endian
> ./ld-new: failed to merge target specific data of file tmpdir/jli-overflow.o
> tmpdir/jli-overflow.o: In function `test_1025':
> (.text+0x2004): relocation truncated to fit: R_ARC_JLI_SECTOFF against
> symbol `__jli.func1025' defined in .jlitab[.jlitab.func1025] section in tmpdir/jli-
> overflow.o
> ./ld-new: final link failed: Symbol needs debug section which does not exist
>
> Could you take a look at this please ?
>
> Cheers
> Nick
next prev parent reply other threads:[~2017-07-20 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 13:48 Nick Clifton
2017-07-20 10:12 ` Claudiu Zissulescu [this message]
2017-07-20 17:11 ` Claudiu Zissulescu
2017-07-21 9:22 ` Nick Clifton
2017-07-24 8:14 ` Claudiu Zissulescu
-- strict thread matches above, loose matches on Subject: below --
2016-04-15 8:18 Nick Clifton
2016-04-15 9:12 ` Claudiu Zissulescu
2016-04-17 20:29 ` Andrew Burgess
2016-04-19 16:46 ` Andrew Burgess
2016-04-19 16:57 ` Claudiu Zissulescu
2016-04-19 18:32 ` Andrew Burgess
2016-04-20 9:11 ` Claudiu Zissulescu
2016-04-20 9:29 ` Nick Clifton
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=098ECE41A0A6114BB2A07F1EC238DE89666309AB@de02wembxa.internal.synopsys.com \
--to=claudiu.zissulescu@synopsys.com \
--cc=John.Martin@emmicro-us.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).