From 387dd77738619d7e898f063bbeb1b8b6faf6cad5 Mon Sep 17 00:00:00 2001 From: Dilyan Palauzov Date: Fri, 27 Jan 2017 13:20:24 +0000 Subject: Update description of the -plugin option used by the linker, ar and nm. PR 20343 ld * ld.texinfo (Options): Extend documentation of the --plugin option. Include a description of where the plugins should be located. binutils* doc/binutils.texi (ar): Extend documentation of the --plugin option. Include a description of where the plugins should be located. (nm): Likewise. --- ld/ld.texinfo | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'ld/ld.texinfo') diff --git a/ld/ld.texinfo b/ld/ld.texinfo index 29c2131..2ce7560 100644 --- a/ld/ld.texinfo +++ b/ld/ld.texinfo @@ -828,6 +828,22 @@ the linker may make more use of this option. Also currently there is no difference in the linker's behaviour for different non-zero values of this option. Again this may change with future releases. +@kindex -plugin @var{name} +@item -plugin @var{name} +Involve a plugin in the linking process. The @var{name} parameter is +the absolute filename of the plugin. Usually this parameter is +automatically added by the complier, when using link time +optimization, but users can also add their own plugins if they so +wish. + +Note that the location of the compiler originated plugins is different +from the place where the @command{ar}, @command{nm} and +@command{ranlib} programs search for their plugins. In order for +those commands to make use of a compiler based plugin it must first be +copied into the @file{$@{libdir@}/bfd-plugins} directory. All gcc +based linker plugins are backward compatible, so it is sufficient to +just copy in the newest one. + @kindex --push-state @cindex push state governing input file handling @item --push-state -- cgit v1.1