search for: passunit

...s compiled with @@ -186,6 +188,116 @@ typedef ModulePassManager PMType; }; +// TODO: Start migration towards a single passmanagert. This PMT will manage +// all passes as one, rather than having any sort of hierarchy. The trick is +// to have all the passes wrapped into a single abstract PassUnit. Each +// PassUnit will then have concrete implmentations for all the various +// passes, such as, module, function, basicblock, loop, callgraphscc, and +// immutable. These PassUnit will provide a single point of entry as an +// interface while its concrete implementations will handle all th...

The patch below basically hammers out some ideas as to where I'd like to take the passmanager in LLVM. I've tried thinking things through, but I'm still a n00b, so some criticism would be more than welcome. =) Starting from line 191 down. If you're wondering why I created a patch, well that's because I found thinking in passmanagert.h the most productive. -- Regards.

On 1/10/06, Chris Lattner <sabre at nondot.org> wrote: > Interesting approach. :) Thanks. > Comments below, with ***'s before the notes: > +class LoopPass : public Pass {}; // Temporary. > > *** I wouldn't worry about loop passes yet. Sure. > +class PassUnit { > + Pass *pass; > + > + enum Traversal { > + LINEAR, // Standard top down traversal. > + CALLGRAPHSCC // Bottom Up Traversal > + }; > + > + Traversal traversal; > > *** 'Traversals' as you have them here don't really make sense. The > n...