This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Fwd: LLVM collaboration?
- From: Rafael EspÃndola <rafael dot espindola at gmail dot com>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: Jan Hubicka <hubicka at ucw dot cz>, Renato Golin <renato dot golin at linaro dot org>, gcc <gcc at gcc dot gnu dot org>
- Date: Wed, 12 Feb 2014 08:15:15 -0500
- Subject: Re: Fwd: LLVM collaboration?
- Authentication-results: sourceware.org; auth=none
- References: <CAMSE1kdfpeLp6NEc+jnEWqi0KWV-+=Q701UsiLhgcn13X6fYcA at mail dot gmail dot com> <CAMSE1ke32x19T07uidRJWiOpYDs3eSnKEL3u_dDHxBHJQR84cg at mail dot gmail dot com> <20140211022910 dot GA31962 at atrey dot karlin dot mff dot cuni dot cz> <CAMSE1kdp5RQhsLTAYpshBvOrYVBY=9Y_hZDq6cNQk837a88cbA at mail dot gmail dot com> <CAMSE1kd=1dAv-ux9L6yTdNT03kAdEHGQo+L0-RwEWaEF3Nka4g at mail dot gmail dot com> <CAG3jReKSj7HL-Tpgyx5jyoEbu-p-Jh1g+k-ghVHZQet26w=cyQ at mail dot gmail dot com> <20140211212020 dot GB7400 at kam dot mff dot cuni dot cz> <CAFiYyc0ttm34x6poZPg5kiSH78iUbyjRrb6y+WrhpOGQjWHz9g at mail dot gmail dot com>
> What about instead of our current odd way of identifying LTO objects
> simply add a special ELF note telling the linker the plugin to use?
>
> .note._linker_plugin '/...../libltoplugin.so'
>
> that way the linker should try 1) loading that plugin, 2) register the
> specific object with that plugin.
>
> If a full path is undesired (depends on install setup) then specifying
> the plugin SONAME might also work (we'd of course need to bump
> our plugins SONAME for each release to allow parallel install
> of multiple versions or make the plugin contain all the
> dispatch-to-different-GCC-version-lto-wrapper code).
Might be an interesting addition to what we have, but keep in mind
that LLVM uses thin non-ELF files. It is also able to load IR from
previous versions, so for LLVM at least, using the newest plugin is
probably the best default.
> Richard.
Cheers,
Rafael