search for: newpmdriv

...egister arbitrary callbacks and execute them as pass manager traverses > through the pass pipeline. > > PassInstrumentationCallbacks are indeed the entity to register your > callbacks into, before passing it to PassBuilder; > You can check how it is being done in > `llvm/tools/opt/NewPMDriver.cpp`llvm::runPassPipeline. > > StandardInstrumentations are just a few "standard" callbacks that provide > "standard" functionality, like -print-after-all or -time-passes. > StandardInstrumentations registers its individual instrumentations the > same way you wo...

...999/work/llvm-9999-abi_x86_64.amd64/tools/opt/Release/BreakpointPrinter.o /mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/tools/opt/Release/GraphPrinters.o /mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/tools/opt/Release/NewPMDriver.o /mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/tools/opt/Release/PassPrinters.o /mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/tools/opt/Release/Passes.o /mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/l...

Hello all, Is there a way to register callback that runs before/after passes? PassTimingInfo seems to do a similar thing by calling PassInstrumentationCallbacks::registerBeforePassCallback / registerAfterPassCallback, but it is hard-wired with StandardInstrumentations class. Do we have something similar to RegisterStandardPasses, so custom callbacks can be added from somewhere outside LLVM?

Hi all, I'm porting some LLVM plugins to the new pass manager and I've noticed that the command line options are no longer registered when using `-load-pass-plugin` (the new PM flag) to load the plugins in opt. Everything is back to normal when loading via `-load` (the legacy PM). For example, given this CL option: static cl::opt<bool> SomeFlat("some-flag",

Hi all, I am trying to use LLVM's AliasAnalysis pass, but from a standalone tool that uses llvm libraries. The following is the code snippet I am currently using. PassBuilder PB; auto mod_manager = ModuleAnalysisManager { }; PB.registerModuleAnalyses(mod_manager); AAResults& AAR = mod_manager.getResult<AAManager>(*M); But the code fails at .getResult with the following error:

...RReader InstCombine Instrumentation MC ObjCARCOpts ScalarOpts Support Target TransformUtils Vectorize Passes ExecutionEngine ) # Support plugins. set(LLVM_NO_DEAD_STRIP 1) add_llvm_tool(opt AnalysisWrappers.cpp BreakpointPrinter.cpp Debugify.cpp GraphPrinters.cpp NewPMDriver.cpp PassPrinters.cpp PrintSCC.cpp opt.cpp DEPENDS intrinsics_gen ) export_executable_symbols(opt) if(WITH_POLLY AND LINK_POLLY_INTO_TOOLS) target_link_libraries(opt PRIVATE Polly) endif(WITH_POLLY AND LINK_POLLY_INTO_TOOLS) target_link_libraries(opt PUBLIC LLVMExecutionEngine) ``...

Hey: I spent sometime debugging this, it seems like editing ``llvm/tools/opt.cpp`` and move ``cl::ParseCommandLineOptions(argc, argv, "llvm .bc -> .bc modular optimizer and analysis printer\n");`` to the beginning of main() solved it for me. I'm not sure if this is a bug on LLVM side Zhang ------------------ Original ------------------ From: "Viktor Was BSc via

...mpiling GraphPrinters.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts Shared Library cygLTO.dll llvm[2]: ======= Finished Linking Release+Asserts Executable llvm-as (without symbols) make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-as' llvm[2]: Compiling NewPMDriver.cpp for Release+Asserts build llvm[2]: ======= Finished Linking Release+Asserts Executable llvm-dis (without symbols) make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-dis' llvm[2]: Building Release+Asserts Archive Library libLTO.a llvm[2]: Compiling PassPrinters.cpp...