search for: livevariableanalysi

...o explore too deeply yet (the stack trace >> doesn't >> give any useful information) but I suspect Pass is the register >> allocator >> and RequiredPass is the coalescer. > > Turns out I was wrong. Pass is the register allocator but > RequiredPass is > LiveVariableAnalysis. Any idea why this would cause a problem? > If in register allocator you have requested another higher level pass after LiveVariableAnalysis pass then this may happen. - Devang

On Wednesday 25 July 2007 17:29, Devang Patel wrote: > In simple words, pass manager is not able to schedule passes in > requested order. Pass manager is not able to find required pass at the same > level (module, function, loop etc..) or higher level compared current pass. Ok, that gives me some ideas. I didn't understand what "level" means. > What is Pass and

...ion hits ? > > I haven't had a chance to explore too deeply yet (the stack trace doesn't > give any useful information) but I suspect Pass is the register allocator > and RequiredPass is the coalescer. Turns out I was wrong. Pass is the register allocator but RequiredPass is LiveVariableAnalysis. Any idea why this would cause a problem? -Dave

On Thursday 26 July 2007 11:48, Devang Patel wrote: > If in register allocator you have requested another higher level pass > after LiveVariableAnalysis pass then this may happen. Can you explain why this is so? I would assume that I could declare Pass dependencies in any order. The manual certainly doesn't say anything about restricions like this. Shouldn't a Pass just be a Pass that can be run?...

...ing some methods > from LLVM > to > indicate the folding. > Hi Fernando, It's hard to say exactly what's happening because I don't know your code (though, from the stack trace, it seems like there's some sort of memory debacle), but looking at the comment in the LiveVariableAnalysis.cpp file where it's folding memory operands, it might explain somethings better: // Folding the load/store can completely change the instruction in // unpredictable ways, rescan it from the beginning. It's after this that it re-analyzes the operands of the m...

Dear LLVMers, I am trying to fold memory operands in the way that is done in RegAllocLocal.cpp, or in LiveIntervalAnalysis.cpp, but I am getting errors that I don't know how to fix. Could someone tell me which steps should I take in order to correctly fold memory operands? The code that I am using is: const TargetMachine & target_machine = this->machine_function->getTarget();

On Jul 26, 2007, at 11:25 AM, David Greene wrote: > On Thursday 26 July 2007 11:48, Devang Patel wrote: > >> If in register allocator you have requested another higher level pass >> after LiveVariableAnalysis pass then this may happen. > > Can you explain why this is so? I would assume that I could > declare Pass > dependencies in any order. The manual certainly doesn't say > anything about > restricions like this. Shouldn't a Pass just be a Pass that can be > run?...

> Hi Fernando, > > It's hard to say exactly what's happening because I don't know your > code (though, from the stack trace, it seems like there's some sort > of memory debacle), but looking at the comment in the > LiveVariableAnalysis.cpp file where it's folding memory operands, it > might explain somethings better: > > // Folding the load/store can completely change the > instruction in > // unpredictable ways, rescan it from the beginning. > > It's after this that it re-a...