search for: passinf

Displaying 9 results from an estimated 9 matches for "passinf".

Did you mean: passing
2012 Jun 28
1
[LLVMdev] Any way to use a pass in opt, that does not have normal constructor?
Dear LLVM, The TargetData pass needs target data layout to be specified in constructor, and therefore its normal ctor is defined, but always gives a fatal error. Still, is there any way to make it loadable into the opt tool? I need this to make use of bugpoint in reducing backend test case. Thanks, - Dima.
2013 Dec 25
3
[LLVMdev] Crash in opt.cpp:739 when loading custom pass (only on system-wide debug install of llvm)
Hi, I'm trying to write custom pass. However opt started crashed in opt.cpp. After debugging it looks like PassInf->NormalCtor points to unmapped memory (rest of struct contains correct data about my pass) - it pointed high in user memory (0x756e672e006e6f69). It happens only when I tried to install debug version of llvm system-wide (I've check that it wasn't caused by stale .a files). When I used t...
2010 Mar 14
3
[LLVMdev] [PATCH] Before/After IR Dumps
...lude "llvm/Assembly/PrintModulePass.h" #include "llvm/Assembly/Writer.h" #include "llvm/Support/CommandLine.h" You don't need this #include. +// Register a pass and add options to dump the IR before and after it +// is run +typedef llvm::cl::list<const llvm::PassInfo *, bool, PassNameParser> +PassOptionList; This comment is out of date. +// Print IR out before/after specified passes +PassOptionList +PrintBefore("print-before", + llvm::cl::desc("Print IR before specified passes")); Please properly punctuate your comment. +...
2010 Mar 12
0
[LLVMdev] [PATCH] Before/After IR Dumps
On Friday 12 March 2010 08:13:05 Kalle Raiskila wrote: > David Greene wrote: > > Here's a rework using PassManager as Chris suggested. Comments? > > Tried this second patch with the svn version 97812 (the one the patch is > made against), but it doesn't compile: > "llvm/include/llvm/Pass.h:127: Error: expected unqualified-id before "&" >
2010 Mar 12
2
[LLVMdev] [PATCH] Before/After IR Dumps
David Greene wrote: > Here's a rework using PassManager as Chris suggested. Comments? Tried this second patch with the svn version 97812 (the one the patch is made against), but it doesn't compile: "llvm/include/llvm/Pass.h:127: Error: expected unqualified-id before "&" token" Seems raw_ostream is forward declared but not defined (adding a missing #include
2010 Mar 15
0
[LLVMdev] [PATCH] Before/After IR Dumps
...s.h" > #include "llvm/Assembly/Writer.h" > #include "llvm/Support/CommandLine.h" > > You don't need this #include. Ok. > +// Register a pass and add options to dump the IR before and after it > +// is run > +typedef llvm::cl::list<const llvm::PassInfo *, bool, PassNameParser> > +PassOptionList; > > This comment is out of date. Not sure, I'll check. > +// Print IR out before/after specified passes > +PassOptionList > +PrintBefore("print-before", > + llvm::cl::desc("Print IR before specified...
2016 Mar 24
0
Help with pass manager
The problems happens because PMTopLevelManager::findAnalysisPassInfo(AnalysisID AID) returns nullptr in PMTopLevelManager::addImmutablePass(ImmutablePass *P). This because PassRegistry::getPassRegistry()->getPassInfo(AID) call in it returns nullptr as well. Should I probably register the pass I want to add with PassRegistry::registerPass(const PassInfo &PI,...
2016 Mar 30
1
Help with pass manager
...before they are added into a pass manager. Are you calling TargetLibraryInfoWrapperPass::initializePass anywhere? -Chris > On Mar 24, 2016, at 10:41 AM, Lorenzo Laneve via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The problems happens because PMTopLevelManager::findAnalysisPassInfo(AnalysisID AID) returns nullptr in PMTopLevelManager::addImmutablePass(ImmutablePass *P). > This because PassRegistry::getPassRegistry()->getPassInfo(AID) call in it returns nullptr as well. > Should I probably register the pass I want to add with PassRegistry::registerPass(const PassInfo...
2016 Mar 24
2
Help with pass manager
...errs() << "start-after and/or stop-after passes are redundant when run-pass is specified.\n"; >>>>>>>>>> return 1; >>>>>>>>>> } >>>>>>>>>> const PassInfo *PI = PR->getPassInfo(RunPass); >>>>>>>>>> if (!PI) { >>>>>>>>>> errs() << "run-pass pass is not registered.\n"; >>>>>>>>>> return 1; >>&gt...