search for: passcollect

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.

...mentations 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 the pass +// specific details. Then a two types of PassCollection will be required, +// one ordered and another unordered. This will allow either batches of +// Passes which can be run in parallel (unordered) or a sequence of Passes +// which depend upon each other. + +//The following is the foundation for the above. + +class PassUnit { + Pass *pass; + +...

...ture themselves. Can you explain a bit more? The idea is to provide a wrapper to hide any pass specific logic that's required for pass management. They don't really capture a lot of information right now but that's because they're more geared towards being method heavy. > +// PassCollection and its implmentations will actually posses a significant > +// amount of the logic in terms of handling passes. The passmanager will > in > +// fact be a simple interface and entry point. > > "Just a quick little tid bit, that's rather important. The > PassCollectio...