search for: verifyanalysis

...SSA pass without introducing circular dependency between TransformUtils and Analysis libraries. I have couple of solutions in mind but wanted to ask your opinion on those, maybe we will be able to arrive at better decision. >> >> 1. I can introduce list of loops which LCSSAWrapperPass::verifyAnalysis needs to verify. It will be stored in the LoopInfo and populated in the LPPassManager main loop. After verification LCSSAWrapperPass will remove loop from this list. > >> >> 2. There could be separate analysis “LCSSAVerification” on which LCSSA pass will depend. That way I will be...

...oop/list of loops to verify to the function pass. Instead, I think it would be easier to create a loop pass for LCSSAVerification and make all loop passes preserve it. > > This way, when LPM would be verifying preserved analysis, it’ll run the LCSSA verification for the current loop as well (verifyAnalysis from the new pass). We can make it depend on the existing LCSSA pass, so that requiring this one would result in building LCSSA if it’s not built yet. The verification itself will be moved from the existing LCSSA pass’s verifyAnalysis to the new pass’s verifyAnalysis (or we can keep verification in...

Hi Nick I am not quite sure what you meant by verifier. I checked online documents and found that there is a function verifyAnalysis() in Pass but it is empty. So do you suggest implementing that function? If it is the case, what should I look while implementing that function? Or something else altogether? Thanks, Nehal. -----Original Message----- From: Nick Lewycky [mailto:nicholas at mxc.ca] Sent: Friday, June 04, 2010 2:29...

Nehal Gandhi wrote: > Hi Nick > > I am not quite sure what you meant by verifier. I checked online documents > and found that there is a function verifyAnalysis() in Pass but it is empty. > So do you suggest implementing that function? If it is the case, what should > I look while implementing that function? Or something else altogether? I'm assuming you have a PassManager PM, in which case it would be 'PM.add(createVerifierPass());' wh...

...anager contains LCSSA pass without introducing circular dependency between TransformUtils and Analysis libraries. I have couple of solutions in mind but wanted to ask your opinion on those, maybe we will be able to arrive at better decision. 1. I can introduce list of loops which LCSSAWrapperPass::verifyAnalysis needs to verify. It will be stored in the LoopInfo and populated in the LPPassManager main loop. After verification LCSSAWrapperPass will remove loop from this list. 2. There could be separate analysis “LCSSAVerification” on which LCSSA pass will depend. That way I will be able to recognise it in...

...nformation > through all the transformation passes and make it available to the > backend machinery. > > Attached is an example patch on how I plan to preserve the information > for a given transformation pass. At a brief glance, this looks good. It would be helpful to override the verifyAnalysis method from the Pass class to verify that the profiling information has been kept current. > > And now comes the question into place: whats the best way to attach > the > profile info also the MachineBlocks and MachineFunctions? I was > thinking > of converting the ProfileInf...

...op in the function every time. That level of checking can be > // enabled with the -verify-loop-info option. > { > TimeRegion PassTimer(getPassTimer(&LIWP)); > CurrentLoop->verifyLoop(); > } > > // Then call the regular verifyAnalysis functions. > verifyPreservedAnalysis(P); > > F.getContext().yield(); > } > > Was it intentional that verifyPreservedAnalysis is under > !LoopWasDeleted condition? Will anything break if we move > verifyPreservedAnalysis out of the if? Seems like a mist...

Have you tried running the verifier after ConditionProfile runs? Just add it to the pass manager to run right afterwards and see what it picks up. Nick Nehal Gandhi wrote: > > > Hi All, > > I am trying to write code for simple instrumentation. What I want to do > is to insert a call to an external function for result of each > conditional branch instruction. This external

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, the second part of my work is to preserve the profiling information through all the transformation passes and make it available to the backend machinery. Attached is an example patch on how I plan to preserve the information for a given transformation pass. And now comes the question into place: whats the best way to attach the profile info

...::releaseMemory() ld: 0711-317 ERROR: Undefined symbol: llvm::Pass::getAdjustedAnalysisPointer(void const*) ld: 0711-317 ERROR: Undefined symbol: llvm::Pass::getAsImmutablePass() ld: 0711-317 ERROR: Undefined symbol: llvm::Pass::getAsPMDataManager() ld: 0711-317 ERROR: Undefined symbol: llvm::Pass::verifyAnalysis() const ld: 0711-317 ERROR: Undefined symbol: llvm::Pass::dumpPassStructure(unsigned int) ld: 0711-317 ERROR: Undefined symbol: llvm::FunctionPass::doInitialization(llvm::Module&) ld: 0711-317 ERROR: Undefined symbol: llvm::FunctionPass::doFinalization(llvm::Module&) ld: 0711-317 ERROR: Und...

Hi All, I am trying to build llvm on AIX. I installed all the required packages including gcc, g++, etc ./configure also went fine. but i tried to run gmake, i got the following error: llvm[1]: Compiling MemoryBuffer.cpp for Release+Asserts build llvm[1]: Compiling MemoryObject.cpp for Release+Asserts build llvm[1]: Compiling Mutex.cpp for Release+Asserts build llvm[1]: Compiling Path.cpp for

Hi All, I am trying to write code for simple instrumentation. What I want to do is to insert a call to an external function for result of each conditional branch instruction. This external function simply print true or false based on the result of condition. The modified code is then written into new file. However when I try to link that file with another bitcode file (containing external

...Assert/llvm-objects/tools/opt/Debug+Asserts/opt.o llvm::PassNameParser::~PassNameParser()/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/opt.o llvm::createDeadArgEliminationPass() /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/opt.o llvm::Pass::verifyAnalysis() const /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/AnalysisWrappers.o llvm::createEarlyCSEPass() /n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/opt.o llvm::ValueHandleBase::AddToExistingUseList(llvm::ValueHandleBase**)/n/fs/scratch/tpond...