search for: try_calls_basic2

...ted seems it is not (although the result is guaranteed to be the same). Now I think the order functions are processed might not be guaranteed. I've attached a test case, and here is what I get: ............................... (303)$ ~/bin/llvm/bin/gcc -O3 -emit-llvm try_calls_basic.2.c -c -o try_calls_basic2.bc (304)$ $LLVM/opt -O3 -IR-DUMP :ALL -load ~/download/llvm-objects/Debug/lib/LLVMHello.so -hello -debug-pass Structure < try_calls_basic2.bc > try_calls_basic2.2.bc 2> x1 (305)$ $LLVM/opt -O3 -IR-DUMP :ALL -load ~/download/llvm-objects/Debug/lib/LLVMHello.so -hello -debug-pass Str...

On Mon, May 18, 2009 at 8:33 PM, dan mihai <dnmh68 at hotmail.com> wrote: > Hello, > Yo! > For debugging purposes, I've added a unique id member to the Value class: > > global_next_vuid = 0; > Value::Value(..){ >   vuid = ++global_next_vuid; > } > > My hope is that by looking at the vuid of a Value, I can see its vuid, > set a conditional breakpoint and

Hello, For debugging purposes, I've added a unique id member to the Value class: global_next_vuid = 0; Value::Value(..){ vuid = ++global_next_vuid; } My hope is that by looking at the vuid of a Value, I can see its vuid, set a conditional breakpoint and re-run the compiler to see who (what pass) constructed that value. Maybe I am not doing it the right way, but the above 'vuid'