[LLVMdev] [RFC] New ToolsSupport library for stuff that only tools need

[Chandler Carruth]

On Fri, Nov 7, 2014 at 12:20 PM, Owen Anderson <resistor at mac.com> wrote:

> On Nov 7, 2014, at 8:57 AM, Daniel Dunbar <daniel at zuster.org> wrote:
>
> 2. I agree with Chandler in that I don't see a good need to try hard to
> factor out code from the Support library that can just be conditional
> disabled or would be unused by normal .a link semantics. For example,
> whether or not the regex or YAML code belongs in Support doesn't seem worth
> worrying too much about, because they are very isolated, don't introduce
> extra dependencies, and won't be linked by projects that don't use them.
>
>
> This assumes that the client is statically linking against Support.  Chris
> has been pretty explicit about his goals of building and using LLVM as a
> monolithic dynamic library, in which case things like regex or YAML support
> will *not* be automatically removed.
>

I see...

Maybe what we really need is (lacking a complete export list for the
monolithic dynamic library) to use visibility so that these kinds of things
can be dropped from the final dynamic library if they aren't used within
it? I suspect would could mark essentially all of the support library, as
unless it is used in the interface of some other library, we probably don't
want to export it... (Having just started thinking about this, I've no idea
whether folks using the LLVM dynamic library are independently using bits
of the ADT for example....)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141107/e5b9a620/attachment.html>