search for: moduleprinter

...gt;> -print-after-all >> >> This patch looks very invasive for such a simple thing, isn't there a >> better way? > > Possibly. What specifically do you object to? The main problem is that > one needs different printers at different stages of the compiler: > ModulePrinter, FunctionPrinter and MachineFunctionPrinter. It makes > sense to write the code once and parameterize it on the printer type. > > I see addPass<> as the most "invasive" in the sense that the patch > changes almost every call of PM.addPass(..) to addPass<>(PM, ......

...t; > > -print-before-all > > -print-after-all > > This patch looks very invasive for such a simple thing, isn't there a > better way? Possibly. What specifically do you object to? The main problem is that one needs different printers at different stages of the compiler: ModulePrinter, FunctionPrinter and MachineFunctionPrinter. It makes sense to write the code once and parameterize it on the printer type. I see addPass<> as the most "invasive" in the sense that the patch changes almost every call of PM.addPass(..) to addPass<>(PM, ...). That's a cons...

On Mar 2, 2010, at 1:45 PM, David Greene wrote: > This set of patches adds support for dumping IR before or after specified > Passes. It adds the following command-line options: > > -print-before=<pass-option> > -print-after=<pass-option> > -print-before-all > -print-after-all This patch looks very invasive for such a simple thing, isn't there a better

This set of patches adds support for dumping IR before or after specified Passes. It adds the following command-line options: -print-before=<pass-option> -print-after=<pass-option> -print-before-all -print-after-all Use it like this: llc -debug -print-before=linearscan-regalloc file.bc -o file.s -help will print the pass options available to -print-before and -print-after. The