search for: identifcation

Displaying 5 results from an estimated 5 matches for "identifcation".

Did you mean: identification
2013 Feb 08
0
[LLVMdev] llvm metadata transformation pass
...transformations are not applied on the .bc of the target program. The Test1.bc (clean) and Test2.bc (transformation applied) are the same. I just have using namespace llvm; namespace { struct metadata : public FunctionPass { const Function *F; static char ID; // Pass identifcation, replacement for typeid metadata() : FunctionPass(ID) { //initializeMemDepPrinterPass(*PassRegistry::getPassRegistry()); } virtual bool runOnFunction(Function &F); virtual void getAnalysisUsage(AnalysisUsage &AU) const { AU.setPreservesAll...
2013 Feb 13
0
[LLVMdev] write a transformation pass
..., but the Test.bc file is not modified (still have " %myDimension = alloca %class.ThreeDimension, align 4 "). Can you tell me how can I make the transformations persistent? I have : namespace { struct metadata : public FunctionPass { const Function *F; static char ID; // Pass identifcation, replacement for typeid metadata() : FunctionPass(ID) { //initializeMemDepPrinterPass(*PassRegistry::getPassRegistry()); } virtual bool runOnFunction(Function &F); virtual void getAnalysisUsage(AnalysisUsage &AU) const { AU.setPreservesAll(); } // virtual...
2003 Apr 06
1
[Bug 537] Identification should depend on port number
...t.org at tange.dk I run 2 completely seperate sshds on different ports. The sshds are used for different purposes and therefore use different configurations. Normally people will only connect to one of the the 2 sshds, but a few people need to connect to both. This makes sshd complain that the identifcations has changed - even though it has not. It would be nice if the identification is not only made on (name, IP address) but on (name, IP address, port number). ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
2007 Jul 13
0
[LLVMdev] [PATCH] Re: Pluggable Register Coalescers
...nction already. + /// This allows the coalescer to either run independently or from + /// within a register allocator. + typedef std::map<const MachineFunction *, bool> WorkMap; + WorkMap didWork; + void doWork(MachineFunction &mf); + public: static char ID; // Pass identifcation, replacement for typeid SimpleRegisterCoalescing() : MachineFunctionPass((intptr_t)&ID) {}; + const char *getPassName() const{ + return "Simple Register Coalescing"; + }; + + /// Allow a register allocator to re-run this on a function + void reset(const Machine...
2007 Jul 11
3
[LLVMdev] Pluggable Register Coalescers
On Jul 11, 2007, at 11:39 AM, David Greene wrote: > On Wednesday 11 July 2007 12:41, Tanya M. Lattner wrote: > >> I think the coalescer should be flexible enough to be run >> independent of >> the register allocator. For example, you may want to expose the >> copies >> induced by transforming out of SSA to the scheduler. If the >> scheduler is