This is the mail archive of the
mailing list for the binutils project.
Re: linker plugin api limitation
- From: Rafael EspÃndola <rafael dot espindola at gmail dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>, Cary Coutant <ccoutant at gmail dot com>, Evgenii Stepanov <eugeni dot stepanov at gmail dot com>
- Date: Mon, 22 Feb 2016 11:20:01 -0500
- Subject: Re: linker plugin api limitation
- Authentication-results: sourceware.org; auth=none
- References: <CAG3jReJDT2ZDNRh-cYSSBG76FnrReQWbgFgfsA_gvLdb5zmEEw at mail dot gmail dot com> <CAMe9rOqQnyagQ=4BdfkNgPiAzc9X4B0=BNibChyhJfd3osCcmw at mail dot gmail dot com>
On 22 February 2016 at 11:14, H.J. Lu <email@example.com> wrote:
> On Mon, Feb 22, 2016 at 6:39 AM, Rafael EspÃndola
> <firstname.lastname@example.org> wrote:
>> Evgeniy Stepanov recently found a limitation of the plugin api with
>> --start-lib --end-lib: there is no way to tell the difference from a
>> file not being included in the link to it being included and all the
>> symbols being preempted.
> How should --start-lib --end-lib work? Is there an equivalent command
> line option for BFD ld?
I don't think it is implemented in BFD ld. The idea is that using
$ ld ... --start-lib <objs> --end-lib
should be equivalent to
$ ar rc foo.a <objs>
$ ld ... foo.a
ar is normally very fast, but when doing a fully distributed build one
would still need to copy <objs> to a node just to create foo.a. Using
--start-lib/--end-lib saves that step.
>> There is more information at https://llvm.org/pr26674.
> It should be:
Gah, the pr redirect doesn't work with https, sorry about that.