[LLVMbugs] [Bug 1186] NEW: Assertion failure in PassManager.cpp:643

[bugzilla-daemon at cs.uiuc.edu]

http://llvm.org/bugs/show_bug.cgi?id=1186

           Summary: Assertion failure in PassManager.cpp:643
           Product: libraries
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core LLVM classes
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: babic.domagoj at gmail.com


Build the attached example as loadable module, run -tst3.
Used to work with the old PassManager [last time I updated was Dec 30, 06'].

Domagoj

opt: /work/projects/llvm/lib/VMCore/PassManager.cpp:643: void
llvm::PMDataManager::collectRequiredAnalysisPasses(std::vector<llvm::Pass*,
std::allocator<llvm::Pass*> >&, llvm::Pass*): Assertion `AnalysisPass &&
"Analysis pass is not available"' failed.
opt((anonymous namespace)::PrintStackTrace()+0x17)[0xa1f13b]
opt((anonymous namespace)::SignalHandler(int)+0x10e)[0xa1f40a]
/lib/libc.so.6[0x2aaaab39f1b0]
/lib/libc.so.6(gsignal+0x3d)[0x2aaaab39f11d]
/lib/libc.so.6(abort+0xfe)[0x2aaaab3a084e]
/lib/libc.so.6(__assert_fail+0xf1)[0x2aaaab3988f1]
opt(llvm::PMDataManager::collectRequiredAnalysisPasses(std::vector<llvm::Pass*,
std::allocator<llvm::Pass*> >&, llvm::Pass*)+0xbc)[0x9b1502]
opt(llvm::PMDataManager::add(llvm::Pass*, bool)+0xc1)[0x9b2d31]
opt(llvm::FunctionPass::assignPassManager(llvm::PMStack&,
llvm::PassManagerType)+0x1bb)[0x9b33b9]
opt(llvm::PassManagerImpl::addTopLevelPass(llvm::Pass*)+0xdf)[0x9bb8bf]
opt(llvm::PMTopLevelManager::schedulePass(llvm::Pass*)+0x115)[0x9b0d8b]
opt(llvm::PassManagerImpl::add(llvm::Pass*)+0x24)[0x9b6998]
opt(llvm::PassManager::add(llvm::Pass*)+0x20)[0x9b0db6]
opt((anonymous namespace)::addPass(llvm::PassManager&, llvm::Pass*)+0x1d)[0x761f05]
opt(main+0x5e1)[0x76036b]
/lib/libc.so.6(__libc_start_main+0xdb)[0x2aaaab38c49b]
opt(__gxx_personality_v0+0x12a)[0x75278a]
Aborted



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.