[PATCH] [PM] Create a separate library for high-level pass management code.

Chandler Carruth chandlerc at gmail.com
Wed Mar 4 18:14:48 PST 2015

On Wed, Mar 4, 2015 at 8:01 AM, hfinkel at anl.gov <hfinkel at anl.gov> wrote:

> > The class is a "PassBuilder" but this name I'm less happy with. It
> doesn't build passes in any traditional sense and isn't a Builder-style API
> at all. The class is a PassRegisterer or PassAdder, but neither of those
> really make a lot of sense. This class is responsible for constructing
> passes for registry in an analysis manager or for population of a pass
> pipeline. If anyone has a better name, I would love to hear it. The other
> candidate I looked at was PassRegistrar, but that doesn't really fit
> either. There is no register of all the passes in use, and so I think
> continuing the "registry" analog outside of the registry of pass *names*
> and *types* is a mistake. The objects themselves are just objects with the
> new pass manager.
> A little verbose, but how about something like PassPipelineBuilder?

It isn't just building pipelines though. It also builds analysis passes in
order to register them with the analysis manager.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150304/c8f07fb0/attachment.html>

More information about the llvm-commits mailing list