From: Christophe Lyon <christophe.lyon@linaro.org>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: Alan Modra <amodra@gmail.com>, Nick Clifton <nickc@redhat.com>,
binutils <binutils@sourceware.org>
Subject: Re: [PATCH] PR ld/21233: Avoid sweeping forced-undefined symbols in section GC
Date: Wed, 19 Apr 2017 13:55:00 -0000 [thread overview]
Message-ID: <CAKdteOb8HLF6g42eg88tOeZKXxNgqDwgXsGsXqN1pCw8wPpQ6g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1704191344350.25796@tp.orcam.me.uk>
On 19 April 2017 at 14:52, Maciej W. Rozycki <macro@imgtec.com> wrote:
> On Wed, 19 Apr 2017, Christophe Lyon wrote:
>
>> I've noticed that these tests fail on aarch64 and arm targets:
>>
>> ./ld/ld.sum:FAIL: PR ld/21233 dynamic symbols with section GC (--undefined)
>> ./ld/ld.sum:FAIL: PR ld/21233 dynamic symbols with section GC
>> (--require-defined)
>> ./ld/ld.sum:FAIL: PR ld/21233 dynamic symbols with section GC (EXTERN)
>>
>> Is it a known problem?
>
> I guess it depends to whom. It was certainly discussed and symptoms of
> the problem with the respective backends (though not its cause) identified
> in this thread, and pieces of that consideration were even present in the
> part you quoted.
>
:-) Indeed, it looks like I missed a few parts.
I'm not following binutils closely, but I'm annoyed with seeing my binutils
Jenkins job red :-) (so, I do not plan to fix the problem myself).
I should turn 'make check' into 'make check+compare with previous'
to make sure to catch regressions...
Thanks,
Christophe
next prev parent reply other threads:[~2017-04-19 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 11:39 Maciej W. Rozycki
2017-04-04 8:47 ` Alan Modra
2017-04-04 22:43 ` Maciej W. Rozycki
2017-04-05 2:11 ` Alan Modra
2017-04-05 16:07 ` Maciej W. Rozycki
2017-04-19 12:02 ` Christophe Lyon
2017-04-19 12:52 ` Maciej W. Rozycki
2017-04-19 13:55 ` Christophe Lyon [this message]
2017-04-05 1:13 ` Hans-Peter Nilsson
2017-04-05 16:03 ` Maciej W. Rozycki
2017-04-05 21:38 ` Hans-Peter Nilsson
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=CAKdteOb8HLF6g42eg88tOeZKXxNgqDwgXsGsXqN1pCw8wPpQ6g@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=macro@imgtec.com \
--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).