search for: basicblockpass

...ded from PTXBackend.h:70:0, from PTXBackend.cpp:36: PTXPasses.h: In constructor ‘PTXBackendInsertSpecialInstructions::PTXBackendInsertSpecialInstructions(std::map<const llvm::Value*, const llvm::Value*>&)’: PTXPasses.h:93:63: error: no matching function for call to ‘llvm::BasicBlockPass::BasicBlockPass(char*)’ /home/neelima/Documents/llvm-2.9/include/llvm/Pass.h:321:12: note: candidates are: llvm::BasicBlockPass::BasicBlockPass(char&) /home/neelima/Documents/llvm-2.9/include/llvm/Pass.h:319:36: note: llvm::BasicBlockPass::BasicBlockPass(const llvm::BasicBlockPa...

Hey everybody, good news for everyone interested in the PTX backend: We decided to release the current source code under the GPL - you can find the latest tarball here: http://www.prog.uni-saarland.de/projects/anysl You will find the README in the attachment, which should hopefully answer a lot of questions concerning the implementation and the current status. If you have further questions,

...bug-pass=Details foo.ll -S then I will get this pass structure: Target Library Information Target Transform Information Target Pass Configuration Assumption Cache Tracker Profile summary info ModulePass Manager CallGraph Construction Globals Alias Analysis FunctionPass Manager BasicBlockPass Manager Dead Instruction Elimination Call Graph SCC Pass Manager Function Integration/Inlining FunctionPass Manager Module Verifier Print Module IR FPPassManager:: getAnalysisUsage is doing setPreservesAll(), but is it correct that the FunctionPass Manager alwa...

...f --git a/include/llvm/Transforms/Vectorize.h b/include/llvm/Transforms/Vectorize.h index dfc099d..373d501 100644 --- a/include/llvm/Transforms/Vectorize.h +++ b/include/llvm/Transforms/Vectorize.h @@ -16,7 +16,7 @@  #define LLVM_TRANSFORMS_VECTORIZE_H  namespace llvm { - +class BasicBlock;  class BasicBlockPass;  //===----------------------------------------------------------------------===// @@ -25,6 +25,17 @@ class BasicBlockPass;  //  BasicBlockPass *createBBVectorizePass(); +//===----------------------------------------------------------------------===// +/// @brief Vectorize the BasicBlock. +/// +/...

...on > > Target Transform Information > > Target Pass Configuration > > Assumption Cache Tracker > > Profile summary info > > ModulePass Manager > > CallGraph Construction > > Globals Alias Analysis > > FunctionPass Manager > > BasicBlockPass Manager > > Dead Instruction Elimination > > Call Graph SCC Pass Manager > > Function Integration/Inlining > > FunctionPass Manager > > Module Verifier > > Print Module IR > > > > > > FPPassManager:: getAnalys...

...eJumpTableEntry> >::_M_insert_aux(__gnu_cxx::__normal_iterator<llvm::MachineJumpTableEntry*, std::vector<llvm::MachineJumpTableEntry, std::allocator<llvm::MachineJumpTableEntry> > >, llvm::MachineJumpTableEntry const&) + 2237 14 llc 0x00000001008710b0 llvm::BasicBlockPass::~BasicBlockPass() + 28256 15 llc 0x000000010087116b llvm::BasicBlockPass::~BasicBlockPass() + 28443 16 llc 0x0000000100872822 llvm::BasicBlockPass::~BasicBlockPass() + 34258 17 llc 0x0000000100872b23 llvm::BasicBlockPass::~BasicBlockPass() + 35027 18 llc...

...Das [mailto:sanjoy at playingwithpointers.com] > Sent: den 7 maj 2018 20:22 > To: Björn Pettersson A <bjorn.a.pettersson at ericsson.com>; Chandler > Carruth <chandlerc at google.com> > Cc: llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] Preservation of CallGraph (by BasicBlockPass, > FunctionPass) > > I'm not sure about the old pass manager, but I think the new pass > manager solves this issue. See > llvm::updateCGAndAnalysisManagerForFunctionPass where it updates the > call graph to be in sync with edges deleted by function passes. So I > suspect...

...eJumpTableEntry> >::_M_insert_aux(__gnu_cxx::__normal_iterator<llvm::MachineJumpTableEntry*, std::vector<llvm::MachineJumpTableEntry, std::allocator<llvm::MachineJumpTableEntry> > >, llvm::MachineJumpTableEntry const&) + 2237 14 llc 0x00000001008710b0 llvm::BasicBlockPass::~BasicBlockPass() + 28256 15 llc 0x000000010087116b llvm::BasicBlockPass::~BasicBlockPass() + 28443 16 llc 0x0000000100872822 llvm::BasicBlockPass::~BasicBlockPass() + 34258 17 llc 0x0000000100872b23 llvm::BasicBlockPass::~BasicBlockPass() + 35027 18 llc...

...yingwithpointers.com] > > Sent: den 7 maj 2018 20:22 > > To: Björn Pettersson A <bjorn.a.pettersson at ericsson.com>; Chandler > > Carruth <chandlerc at google.com> > > Cc: llvm-dev at lists.llvm.org > > Subject: Re: [llvm-dev] Preservation of CallGraph (by BasicBlockPass, > > FunctionPass) > > > > I'm not sure about the old pass manager, but I think the new pass > > manager solves this issue. See > > llvm::updateCGAndAnalysisManagerForFunctionPass where it updates the > > call graph to be in sync with edges deleted by functi...

...clude/llvm/Transforms/Vectorize.h > index dfc099d..373d501 100644 > --- a/include/llvm/Transforms/Vectorize.h > +++ b/include/llvm/Transforms/Vectorize.h > @@ -16,7 +16,7 @@ >  #define LLVM_TRANSFORMS_VECTORIZE_H > >  namespace llvm { > - > +class BasicBlock; >  class BasicBlockPass; > >  //===----------------------------------------------------------------------===// > @@ -25,6 +25,17 @@ class BasicBlockPass; >  // >  BasicBlockPass *createBBVectorizePass(); > > +//===----------------------------------------------------------------------===// > +///...

...t; pass requires others BB pass for analysis result, so we had to rewrite > all the passes required by PassA to Function pass, so that PassA can > get the analysis :( Yes, it's inconvenient, but you only have two options: either enhance the PassManager to allow a FunctionPass to use a BasicBlockPass, or modify all of your BasicBlockPass'es to be FunctionPass'es. Personally, I would make everything a FunctionPass. When a lower level pass is requested by a higher level pass (e.g., ModulePass requests a FunctionPass), then the lower-level pass is re-run *even if it was executed prev...

...-Woverloaded-virtual option to compiler to catch such cases. However, it also gives some warnings on LLVM code: ../../../include/llvm/Pass.h:264: warning: `virtual bool llvm::FunctionPass::run(llvm::Module&)' was hidden ../../../include/llvm/Pass.h:326: warning: by `bool llvm::BasicBlockPass::run(llvm::BasicBlock&)' ../../../include/llvm/Pass.h:275: warning: `virtual void llvm::FunctionPass::addToPassManager(llvm::PassManagerT<llvm::Module>*, llvm::AnalysisUsage&)' was hidden ../../../include/llvm/Pass.h:332: warning: by `virtual void llvm::BasicBloc...

...cl::init(false)); Please declare these as static, for the same reasons functions are, and move the end of the anon namespace up. It might also be better to just make this take a list of strings, which would allow you to collapse these to support -print-before=all and -print-after=all. +Pass *BasicBlockPass::createPrinterPass(raw_ostream &O, + const std::string &Banner) const { + return createPrintFunctionPass(Banner, &O); +} + This will disrupt the pass structure. The printer should be a BasicBlockPass. However, BasicBlockPass is probably nearly d...

...liasAnalysis to get a list of aliases for each pointer in a certain program code. First it initializes clang as frontend, executes the EmitLLVMOnlyAction, and then processes the produced Module with the following three passes: 1. BasicAliasAnalysis -- The basic alias analysis 2. AliasTrackerPass -- BasicBlockPass that creates an AliasSet for each pointer in the analyzed code (line 261 and line 94 respectively) 3. AliasDetectorPass -- BasicBlockPass that prints the AliasSet of each pointer in the analyzed code (line 264 and line 133 respectively) The first Pass seems to work flawlessly. However, the 2nd Pas...

hi John, sorry for reply so late. On Tue, Apr 13, 2010 at 10:38 PM, John Criswell <criswell at uiuc.edu> wrote: > Devang Patel wrote: > >> On Mon, Apr 12, 2010 at 6:41 PM, ether zhhb <etherzhhb at gmail.com> wrote: >> >> >> >>> that's because FunctionPass implement the "addLowerLevelRequiredPass" >>> function, but others

On Tue, 30 May 2006, Silken Tiger wrote: > Everthing now compiles fine, but when running llc with invoking my own backend > derived from the cbackend i get the following error: > namespace llvm { > class MParSchedule : public BasicBlockPass { > public: > This pass has been tested as optimization pass with opt, and everything worked > in this configuration. What requires MParSchedule? Note that, since it's a basic block pass, only other basic block passes can require it. If you have a FunctionPass that...

...ass for analysis result, so we had to rewrite all the >> passes required by PassA to Function pass, so that PassA can get the >> analysis :( >> > > Yes, it's inconvenient, but you only have two options: either enhance the > PassManager to allow a FunctionPass to use a BasicBlockPass, or modify all > of your BasicBlockPass'es to be FunctionPass'es. > > Personally, I would make everything a FunctionPass. When a lower level > pass is requested by a higher level pass (e.g., ModulePass requests a > FunctionPass), then the lower-level pass is re-run *even if...

On Monday 15 March 2010 13:45:14 David Greene wrote: > On Sunday 14 March 2010 18:32:35 Chris Lattner wrote: > > This is much better than the first iteration but still has many issues. I believe I've addressed all your points with this patch except I didn't use StringRef. It doesn't appear to be useful since createPrinterPass will be sent a const std::string & and will

Devang Patel wrote: > On Mon, Apr 12, 2010 at 6:41 PM, ether zhhb <etherzhhb at gmail.com> wrote: > > >> that's because FunctionPass implement the "addLowerLevelRequiredPass" >> function, but others not. >> >> so, is there any special reason that only "addLowerLevelRequiredPass" is >> allow? >> >> > >

...ion to compiler to catch such cases. However, it > also gives some warnings on LLVM code: > > ../../../include/llvm/Pass.h:264: warning: `virtual bool > llvm::FunctionPass::run(llvm::Module&)' was hidden > ../../../include/llvm/Pass.h:326: warning: by `bool > llvm::BasicBlockPass::run(llvm::BasicBlock&)' > ../../../include/llvm/Pass.h:275: warning: `virtual void > llvm::FunctionPass::addToPassManager(llvm::PassManagerT<llvm::Module>*, > llvm::AnalysisUsage&)' was hidden > ../../../include/llvm/Pass.h:332: warning: by `virtual void &...