From: Alan Modra <amodra@gmail.com>
To: Stephen Casner <casner@acm.org>
Cc: binutils@sourceware.org
Subject: Re: Plugin tests in ld testsuite
Date: Tue, 16 Jun 2020 12:35:43 +0930 [thread overview]
Message-ID: <20200616030543.GC12881@bubble.grove.modra.org> (raw)
In-Reply-To: <alpine.OSX.2.21.9999.2006111215460.41988@auge.attlocal.net>
On Mon, Jun 15, 2020 at 05:22:09PM -0700, Stephen Casner wrote:
> Now, you could just say that the pdp11-aout code is broken, but the
> code is the same in aoutx.h for the other a.out formats and I don't
> see any code in plugin.exp to exclude them. Do all aout formats get
> an unexpected FAIL for the plugin tests?
I can't answer that since I don't have compilers installed for any of
the few remaining AOUT targets supported by binutils.
> Should the pdp11-aout target be fixed to properly support plugins, or
> is there no point and it should just be configured to disable plugin
> support?
I think you would be pioneering AOUT plugin support if you chose to
support plugins on pdp11. How much of a challenge do you enjoy? :-)
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2020-06-16 3:05 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
2020-05-29 7:20 ` Alan Modra
2020-06-16 0:22 ` Stephen Casner
2020-06-16 3:05 ` Alan Modra [this message]
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=20200616030543.GC12881@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=casner@acm.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).