[PATCH] D85299: [llvm] Support autoloading vendor-defined plugins

[Michał Górny via Phabricator via llvm-commits]

mgorny added a comment.

In D85299#2204692 <https://reviews.llvm.org/D85299#2204692>, @serge-sans-paille wrote:

> I have some difficulties to understand the exact scenario: if one knows at compile-time that polly is needed, why no just build it as a linked-in plugin, as suggested by @Meinersbur?

How does one know that? The whole point is to not have to know what's going to happen in the future, and not have to rebuild the whole LLVM to get Polly or get rid of it. That's pretty much the purpose of plugins, isn't it?

> If one wants to specify a list of auto-loaded plugins at runtime, there's already several ways to do so, either through the C++ API or through CLI.

I don't think we have the same definition of 'auto-loaded'. The whole point is to have them autoloaded in all LLVM tools that might need plugins, *without* manual user effort, and in particular without requiring user to remember the exact paths or having to add wrappers for tools.


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D85299/new/

https://reviews.llvm.org/D85299