search for: add_iter

...Am I missing anything? > > This looks like roughly what I would expect the code to be. I'd have to see the LLVM IR it generated to be sure. But it looks okay to me. (And if it's working for you, all the better. ;-) ) A snippet of the IR code is: > entry: > %add_it = alloca %add_iterator, align 8 > %y_it = alloca %singleton_iterator, align 8 > %x_it = alloca %singleton_iterator, align 8 > %y = alloca %item, align 8 > %x = alloca %item, align 8 > %exception_caught_flag = alloca i8, align 1 > store i8 0, i8* %exception_caught_flag, align 1 > %ca...

On Apr 4, 2012, at 9:32 PM, Paul J. Lucas wrote: > On Mar 23, 2012, at 4:46 PM, Bill Wendling wrote: [...] > This all seems to work just fine. I can throw a C++ exception either in a C++ object's constructor or in an ordinary member function and the stack unwinds correctly (the object's destructors are called) and the exception is propagated back up the C++ code that called the

...the code to be. I'd have to see the LLVM IR it generated to be sure. But it looks okay to me. (And if it's working for you, all the better. ;-) ) > > A snippet of the IR code is: > The code is good, except for one comment (see below). >> entry: >> %add_it = alloca %add_iterator, align 8 >> %y_it = alloca %singleton_iterator, align 8 >> %x_it = alloca %singleton_iterator, align 8 >> %y = alloca %item, align 8 >> %x = alloca %item, align 8 >> %exception_caught_flag = alloca i8, align 1 >> store i8 0, i8* %exception_caught_flag,...