search for: passinfomap

...te *I; - + delete Impl; pImpl = 0; } const PassInfo *PassRegistry::getPassInfo(const void *TI) const { - sys::SmartScopedLock<true> Guard(*Lock); PassRegistryImpl *Impl = static_cast<PassRegistryImpl*>(getImpl()); PassRegistryImpl::MapType::const_iterator I = Impl->PassInfoMap.find(TI); return I != Impl->PassInfoMap.end() ? I->second : 0; } const PassInfo *PassRegistry::getPassInfo(StringRef Arg) const { - sys::SmartScopedLock<true> Guard(*Lock); PassRegistryImpl *Impl = static_cast<PassRegistryImpl*>(getImpl()); PassRegistryImpl::StringMa...

...pt: CommandLine Error: Argument 'help' defined more than once! opt: CommandLine Error: Argument 'help-hidden' defined more than once! opt: CommandLine Error: Argument 'version' defined more than once! opt: Pass.cpp:346: void llvm::RegisterPassBase::registerPass(): Assertion `PassInfoMap->find(PIObj.getTypeInfo()) == PassInfoMap->end() && "Pass already registered!"' failed. Aborted PASS: virtual bool runOnFunction(Function &F) { bool change= false; Function* func = &F; for(Function::iterator it = func->begin(), ite = func ->end(...

> > - gcc bug > > - problem with SuSE distribution > > One of these two. In theory GCC should never crash (even if the LLVM > sources had problems), and since SuSE made modifications to the compiler > before they shipped it, they implicitly took responsibility for the end > result. I agree. > You can try sending a bug report to SuSE. hm, sending bug report is

...to get analysis per SubPassClass): Instead of this: getAnalysis<PassType>() the natural thing would seem to be (for PassClass = MP and SubPassClass = FP): getAnalysis<PassType>(Function) This simple change does mean some big moving in the background, though, since (for starters) the PassInfoMap can't just key on the TypeInfo anymore. It will need to key on something like a structure with TypeInfo and the unit of code that the pass is attached to. I have a feeling there are similar instances where PassInfo needs code-unit info attached to it... Any comments/clarifications/suggestio...

...ense. In the future, only the "ModulePass" class will have this new getAnalysis<T>(Function*) method, but for now it will go into the Pass class (where everyone will get it). > This simple change does mean some big moving in the background, though, > since (for starters) the PassInfoMap can't just key on the TypeInfo > anymore. It will need to key on something like a structure with TypeInfo > and the unit of code that the pass is attached to. I have a feeling > there are similar instances where PassInfo needs code-unit info attached > to it... > > Any comment...

HI, Developers: I linked libLTO.so in $LLVMROOT/Debug/lib however, my program crashes in assertion at 149line [Pass.cpp] void RegisterPass(const PassInfo &PI) { bool Inserted = PassInfoMap.insert(std::make_pair(PI.getTypeInfo(),&PI)).second; assert(Inserted && "Pass registered multiple times!"); } i confirm that there is only one static variable suspecting to call this register routine to register "TargetData" Pass in L35 [TargetData.cpp]...

...ss with the RegisterLLC template. However, when I try to run llc and load up the pass, I get a failed assertion: $ /storage/anshuman/llvmCVS/llvm/tools/Debug/llc -load=./libTest.so --help ... ... llc: Pass.cpp:327: void llvm::RegisterPassBase::unregisterPass(llvm::PassInfo*): Assertion `I != PassInfoMap->end() && "Pass registered but not in map!"' failed. Any ideas why I'm getting this? I've attached the pass code below. (I'm using the cvs version of the LLVM code.) Thanks -Anshu --- Begin pass code --- #include <iostream> #include "llvm/Pass.h...

On Thu, 5 Aug 2004, Michael McCracken wrote: > > You're right that FunctionPass's are not supposed to have state > > (something that many people overlook :) ), however, for now, nothing > > will break if it does have state, and this is really the only way > > around this. > > I'm not sure if I can do this. The pass I'm writing is writing info >

...ass" > class will have this new getAnalysis<T>(Function*) method, but for now > it > will go into the Pass class (where everyone will get it). alright. >> This simple change does mean some big moving in the background, >> though, >> since (for starters) the PassInfoMap can't just key on the TypeInfo >> anymore. It will need to key on something like a structure with >> TypeInfo >> and the unit of code that the pass is attached to. I have a feeling >> there are similar instances where PassInfo needs code-unit info >> attached &gt...

On Aug 5, 2004, at 5:30 PM, Chris Lattner wrote: > On Thu, 5 Aug 2004, Michael McCracken wrote: > >> Hi, I have a hopefully quick question. I'm writing a Pass that needs >> to >> see a whole module at a time and keep some state, so I subclassed >> Pass. >> However, I want to be able to see the Loops in each Function. Roughly, > > ok. > >>