search for: fooaa

...e on 2.7, that doesn't exist in 2.6 as far as I can tell. Short version: has anyone been able to load an AliasAnalysis module into 2.7's opt? Longer version: Even with a dummy pass implementation (just returns MayAlias for everything), I'm getting very strange behavior: All calls to FooAA::alias go to FooAA::print, resulting in understandably painful failure thereafter, generally a segfault. Example stack trace: ==25630== by 0xB2752F: llvm::Pass::print(llvm::raw_ostream&, llvm::Module const*) const (Pass.cpp:94) ==25630== by 0x9B2769: llvm::MemoryDependenceAnalysis::getPo...

...as I can tell. > > Short version: has anyone been able to load an AliasAnalysis module > into 2.7's opt? > > Longer version: > > Even with a dummy pass implementation (just returns MayAlias for > everything), I'm getting very strange behavior: > > All calls to FooAA::alias go to FooAA::print, resulting in > understandably painful failure thereafter, generally a segfault. Are you sure you built your module against LLVM 2.7 headers? -Eli

...version: has anyone been able to load an AliasAnalysis module >> into 2.7's opt? >> >> Longer version: >> >> Even with a dummy pass implementation (just returns MayAlias for >> everything), I'm getting very strange behavior: >> >> All calls to FooAA::alias go to FooAA::print, resulting in >> understandably painful failure thereafter, generally a segfault. > > Are you sure you built your module against LLVM 2.7 headers? > > -Eli > -------------- next part -------------- A non-text attachment was scrubbed... Name: test-aa.ta...

...load an AliasAnalysis module >>> into 2.7's opt? >>> >>> Longer version: >>> >>> Even with a dummy pass implementation (just returns MayAlias for >>> everything), I'm getting very strange behavior: >>> >>> All calls to FooAA::alias go to FooAA::print, resulting in >>> understandably painful failure thereafter, generally a segfault. >>> >> Are you sure you built your module against LLVM 2.7 headers? >> >> -Eli >> > >