From: Stephen Casner <casner@acm.org>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: Plugin tests in ld testsuite
Date: Thu, 28 May 2020 22:43:17 -0700 (PDT) [thread overview]
Message-ID: <alpine.OSX.2.21.9999.2005282236220.1661@auge.attlocal.net> (raw)
In-Reply-To: <20200529031340.GH5475@bubble.grove.modra.org>
On Fri, 29 May 2020, Alan Modra wrote:
> On Tue, May 26, 2020 at 08:43:31PM -0700, Stephen Casner wrote:
> > I'm trying to fix all the unexpected failures for the pdp11-aout
> > target in the gas, ld and binutils testsuites. I fixed a bug in
> > bfd/pdp11.c that allowed "PASS: plugin claimfile lost symbol", but
> > I've been tracing the execution of the next test, "plugin claimfile
> > replace symbol", and I don't see how to fix it. That test fails
> > because the func.o module is claimed by the plugin and yet execution
> > proceeds through loading all the symbols for that module. The test
> > fails because the symbols is _not_ undefined.
> >
> > I am also working on implementation of a pdp11-elf32 target. That
> > target does not use the bfd/pdp11.c code at all, yet the same test
> > fails in the same manner.
> >
> > Is there a target that passes this test so I can compare the execution
> > path? I had hoped to use x86_64-linux-gnu but I have not succeeded in
> > building a cross for that on my MacOS system.
>
> $ grep 'PASS: plugin claimfile lost symbol' */ld/ld.log
Thanks for responding, but that's not the test I was asking about. My
port also passes that one. Please try:
grep 'PASS: plugin claimfile replace symbol' */ld/ld.log
Perhaps that test will also pass for your collection of test cases.
If so, then I just need to get a compiler built for one that does.
-- Steve
next prev parent reply other threads:[~2020-05-29 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 3:43 Stephen Casner
2020-05-29 3:13 ` Alan Modra
2020-05-29 5:43 ` Stephen Casner [this message]
2020-05-29 7:20 ` Alan Modra
2020-06-16 0:22 ` Stephen Casner
2020-06-16 3:05 ` Alan Modra
2020-06-16 19:20 ` Stephen Casner
2020-06-20 22:59 ` Stephen Casner
2020-06-21 7:43 ` Alan Modra
2020-06-21 12:48 ` Do without ld ENABLE_PLUGINS Alan Modra
2020-06-21 12:49 ` PR26132, ar creates invalid libraries for some targets with plugins enabled Alan Modra
2020-06-21 17:24 ` Plugin tests in ld testsuite Stephen Casner
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.OSX.2.21.9999.2005282236220.1661@auge.attlocal.net \
--to=casner@acm.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
/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).