search for: teamplt

...o me. Unless llvm is running on > extremely limited memory embedded systems, the extra code space > shouldn't be an issue. It turns out this wasn't quite a simple as we'd thought. The problem is the CallInst constructors that take two Value * arguments. They look just like the teamplte versions that take iterators. Unfortunately, there is at least one place in llvm where a CallInst is constructed with two AllocaInst pointers. Because the template constructor is a better match, it is selected over the Value * constructors. To get around this problem, I've used SFINAE to re...

On Monday 02 July 2007 16:26, Chris Lattner wrote: > On Sun, 1 Jul 2007, Nick Lewycky wrote: > > I've been running LLVM with _GLIBCXX_DEBUG (extra checks) turned on to > > see what would happen, and it's been a complete disaster. Well, that's a bit harsh, isn't it? It's finding bugs, just like it's supposed to. :) I believe I've started to run into

...ng on >> extremely limited memory embedded systems, the extra code space >> shouldn't be an issue. > > It turns out this wasn't quite a simple as we'd thought. The problem is > the CallInst constructors that take two Value * arguments. They look > just like the teamplte versions that take iterators. Wow, this sounds very complex :) > template<typename InputIterator> > CallInst(Value *Func, InputIterator ArgBegin, InputIterator ArgEnd, > const std::string &Name = "", Instruction *InsertBefore = 0, Is it acceptable to jus...