search for: initializexxxpass

...nter, "print-memdeps", > "Print MemDeps of function", false, true) What's the purpose of the INITIALIZE_PASS_* macros? What's the difference between using static RegisterPass...? When I try to use these macros in user-defined passes. The compiler complains, error: ‘initializeXXXPass’ was not declared in this scope > error: ‘void llvm::initializeXXXPass(llvm::PassRegistry&)’ should have > been declared inside ‘llvm’ Is it because they should only be used by internal LLVM passes? I couldn't find related hints from the documentation. Thanks! ryan -------------- n...

...t; } > // Note that the init_globals() function is pretty mechanical so hopefully easy to understand and maintain. > > We have to call init_gloabals somewhere early: > - Put an init_globals() call into code that runs early. > - We already have a lot of early running functions called initializeXXXPass() which we can use for this > - For the remaining files we probably have to export init_globals() and call it from some common place of the library. > > If someone comes up a with working solution for putting initializers into a section we can later replace the > init_globals() functio...

...nit(); AnotherOpt.init(); } // Note that the init_globals() function is pretty mechanical so hopefully easy to understand and maintain. We have to call init_gloabals somewhere early: - Put an init_globals() call into code that runs early. - We already have a lot of early running functions called initializeXXXPass() which we can use for this - For the remaining files we probably have to export init_globals() and call it from some common place of the library. If someone comes up a with working solution for putting initializers into a section we can later replace the init_globals() function with that so the r...

...e that the init_globals() function is pretty mechanical so hopefully easy to understand and maintain. >> >> We have to call init_gloabals somewhere early: >> - Put an init_globals() call into code that runs early. >> - We already have a lot of early running functions called initializeXXXPass() which we can use for this >> - For the remaining files we probably have to export init_globals() and call it from some common place of the library. >> >> If someone comes up a with working solution for putting initializers into a section we can later replace the >> init_g...

Given that LLVM has so many auto-registration systems (cl::opt, target registry, pass registry, statistics, I'm sure there's more), maybe we should spend the time to build an auto-registration system that doesn't involve static constructors? It needs custom code for every supported object file format, and is hard to get right when DSOs are involved, but in the long run it's

...globals() function is pretty mechanical so hopefully easy to understand and maintain. >>> >>> We have to call init_gloabals somewhere early: >>> - Put an init_globals() call into code that runs early. >>> - We already have a lot of early running functions called initializeXXXPass() which we can use for this >>> - For the remaining files we probably have to export init_globals() and call it from some common place of the library. >>> >>> If someone comes up a with working solution for putting initializers into a section we can later replace the &gt...