From: "H.J. Lu" <hjl.tools@gmail.com>
To: Yuanfang Chen <cyfmxc@gmail.com>
Cc: Andrew Pinski <pinskia@gmail.com>, binutils <binutils@sourceware.org>
Subject: Re: ld -plugin option
Date: Thu, 06 Feb 2014 00:47:00 -0000 [thread overview]
Message-ID: <CAMe9rOqmAxF=DNM-0E_-HGNrR_CAxww2Y_5BJudB1Rr9ne9gKg@mail.gmail.com> (raw)
In-Reply-To: <CAJh9x3p6PkJvCjscoFfd1TdrNQ4UGsAZXoZ1w1pa5aGqjV+r5A@mail.gmail.com>
On Wed, Feb 5, 2014 at 4:33 PM, Yuanfang Chen <cyfmxc@gmail.com> wrote:
> On Wed, Feb 5, 2014 at 7:17 PM, Andrew Pinski <pinskia@gmail.com> wrote:
>> On Wed, Feb 5, 2014 at 4:07 PM, Yuanfang Chen <cyfmxc@gmail.com> wrote:
>>> Hello,
>>>
>>> Maybe this is a silly question, however, it annoys me today for too
>>> long. I'm using ld 2.24, which shows that it supports '-plugin'
>>> option by 'ld --help |grep plugin', however 'ld -plugin' returns
>>> "unrecognized option '-plugin'". I really don't know where the
>>> problem is. Another question is that is the plugin interface
>>> supported by ld and ld.gold the same?
>>
>> Yes the interfaces is the same. The issue you are having is -plugin
>> takes an argument and you are not supplying an option to the -plugin
>> option.
>>
>> Thanks,
>> Andrew Pinski
>
> Well, that's really confusing, I was expecting something like 'missing
> arguments' like the ld.gold does. :-)
>
> I'am asking this because when I'm doing this: (all are non binary object)
> ld.gold -plugin=/path/to/plugin a.o b.o c.o
> everything goes fine.
>
> but
> ld -plugin=/path/to/plugin a.o b.o c.o
> complains b.o: file not recognized: File format not recognized
>
How did you configure binutils? Did you use --enable-plugins?
--
H.J.
next prev parent reply other threads:[~2014-02-06 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 0:07 Yuanfang Chen
2014-02-06 0:17 ` Andrew Pinski
2014-02-06 0:33 ` Yuanfang Chen
2014-02-06 0:47 ` H.J. Lu [this message]
[not found] ` <CAJh9x3pox1d4SL-OGi3NZjbW+1_4VYoSX7LE5g9fVgoUpMo5fw@mail.gmail.com>
2014-02-06 2:28 ` Yuanfang Chen
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='CAMe9rOqmAxF=DNM-0E_-HGNrR_CAxww2Y_5BJudB1Rr9ne9gKg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=cyfmxc@gmail.com \
--cc=pinskia@gmail.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).