[PATCH] Introduce LinkAllPasses.cpp as LLVMAllPasses

Chandler Carruth chandlerc at gmail.com
Wed Jan 15 02:43:57 PST 2014


On Wed, Jan 15, 2014 at 2:39 AM, NAKAMURA Takumi <geek4civic at gmail.com>wrote:

> Although it'd be one of possible fixes, at least in trunk, to add objcarc
> to dragonegg, ...
>
>   Are you really planning to deprecate the way of "show all available
> paths" and to let us update each transforms client (opt, bugpoint, &c)
> whenever passes are added/removed?
>

It's not whenever passes are added/removed.

It's whenever a *library* of passes is added or removed. And it's not even
that bad.

If the pass is used by the PassManagerBuilder, then regardless of the
library it is in, depending on IPO is enough. I think it's fine for clients
of transforms which are not used by any of the standard pass pipeline
building routines to depend explicitly on the library providing those
transforms. They have to have special knowledge of them to use them anyways.


>   Or do you have alternates? I could abandon this patch then.
>

I think this will also get a touch simpler because I plan to create a
library specifically for the PassManagerBuilder and other pass management
logic. It will in turn depend on essentially all transforms. It may not
depend truly on *all* of them, and thats fine. Custom transforms that are
added by custom logic in an extensions point or a plugin seem reasonable to
need custom dependencies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140115/e65503f6/attachment.html>


More information about the llvm-commits mailing list