search for: createstandardfunctionpass

Thanks. The reason I ask is because I'm looking at some code that does just that. A single FunctionPassManager is constructed with a dummy Module and createStandardFunctionPasses is called on it. The FunctionPassManager cached and run on Functions in other Modules. So far I haven't noticed any problems but I guess that is because the passes added by createStandardFunctionPasses don't touch the Module. paul -----Original Message----- From: Nick Lewycky [mailto:ni...

...: > > I've pretty much finished exposing all I wanted to llvm-c and the > ocaml bindings for the soon to be released 2.7. Does anyone need any > other functions exposed before the code freeze on the 7th? > Hi Erick, Can you make the following functions available in llvm-c. createStandardFunctionPasses createStandardModulePasses createStandardLTOPasses Thanks in advance, George

On Fri, Mar 5, 2010 at 5:53 AM, George Giorgidze <giorgidze at gmail.com> wrote: > > Hi Erick, > > Can you make the following functions available in llvm-c. > > createStandardFunctionPasses > createStandardModulePasses > createStandardLTOPasses > > Thanks in advance, George This is a little tricky, so I need some advice from the community. First off, I'm not sure where it's appropriate to put these. For llvm-c, most files live in a header named after the library...

Hi, Is it generally safe to cache a FunctionPassManager and reuse it on modules other than the one it was constructed with (assuming they have the same target triple)? paul -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110923/cd845b59/attachment.html>

On 09/23/2011 11:28 AM, Redmond, Paul wrote: > Hi, > > Is it generally safe to cache a FunctionPassManager and reuse it on > modules other than the one it was constructed with (assuming they have > the same target triple)? No. FunctionPass has a pair of methods, doInitialization and doFinalization, which take Module& and are allowed to read or modify it outside runOnFunction.

I've pretty much finished exposing all I wanted to llvm-c and the ocaml bindings for the soon to be released 2.7. Does anyone need any other functions exposed before the code freeze on the 7th?

...quot; by looking at how the Clang usage had changed, where it previously had used StandardPasses.h and its contents. So, for the release notes, it would be nice to mention this change and perhaps give a couple examples how to convert from calls to "createStandardModulePasses()" and "createStandardFunctionPasses()" to the new interface. Thanks for everyone's hard work on 3.0 - I can't wait to get our project building cleanly with rc2. -Kevin

...fine. - The background compilation also works fine if I comment out the addition of the optimization passes. - The optimization passes are being added as follows: llvm::OwningPtr<llvm::PassManager> passManager( new llvm::PassManager ); if ( optimize ) { llvm::createStandardFunctionPasses( passManager.get(), 2 ); llvm::createStandardModulePasses( passManager.get(), 2, false, true, true, true, false, llvm::createFunctionInliningPass() ); llvm::createStandardLTOPasses( passManager.get(), true, true, false ); } passManager->run( *module ); - If...

...d compilation also works fine if I comment out the addition of the optimization passes. > - The optimization passes are being added as follows: >        llvm::OwningPtr<llvm::PassManager> passManager( new llvm::PassManager ); >        if ( optimize ) >        { >          llvm::createStandardFunctionPasses( passManager.get(), 2 ); >          llvm::createStandardModulePasses( passManager.get(), 2, false, true, true, true, false, llvm::createFunctionInliningPass() ); >          llvm::createStandardLTOPasses( passManager.get(), true, true, false ); >        } >        passManager->run(...

The opt tool uses two helpers to run passes: createStandardFunctionPasses and createStandardModulePasses. How were the passes to be instantiated by each function chosen? There are some FunctionPasses instantiated by createStandardModulePasses which is a bit counterintuitive. I see that all passes added by the user on the command line are added to "Passes"...