This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/70345] Installing liblto_plugin under $LIBDIR/bfd-plugins
- From: "trippels at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 07 Aug 2016 10:45:43 +0000
- Subject: [Bug lto/70345] Installing liblto_plugin under $LIBDIR/bfd-plugins
- Auto-submitted: auto-generated
- References: <bug-70345-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70345
--- Comment #4 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Дилян Палаузов from comment #3)
> Am I correct if I say, that the gcc plugin is backward compatible: the
> plugin from the newest gcc can be used with any gcc but not vice versa?
Right now the plugin from any gcc can be used with any gcc.
But this might change in the future.
> How do nm and ar determine, if a plugin shall be used, for instance when `nm
> test.o` is called?
They get tried in alphabetic order. The first plugin that claims the object in
question is used.
Mixed gcc/llvm archives are also supported.