Displaying 2 results from an estimated 2 matches for "__zti1b".
Did you mean:
_zti1b
2011 Aug 05
0
[LLVMdev] RFC: Exception Handling Rewrite
...set L$set$6,LEHE2-LEHB2
.long L$set$6 # length
.set L$set$7,L20-LFB9
.long L$set$7 # landing pad
.byte 0x5 # uleb128 0x5; action
. . . [ elided for readability ]
.byte 0x7d # Action record table
.byte 0x0
.byte 0x2
.byte 0x7d
.byte 0x7f
.byte 0x7d
.byte 0x0
.byte 0x79
.align 2
.long __ZTI1B+4 at GOTPCREL
.long __ZTIPKc+4 at GOTPCREL
.long __ZTI1A+4 at GOTPCREL
.byte 0x1 # Exception specification table
.byte 0x0
.byte 0x3
.byte 0x0
As you can see, foo() has been completely inlined into bar(). The entry for the call to "baz" (from the foo() function) is shown here in t...
2011 Aug 05
3
[LLVMdev] RFC: Exception Handling Rewrite
Bill,
ooops, yes, I described the meaning of "throw(A)" backwards,
but I still
think my example shows why you cannot merge LandingpadInst while
inlining because multiple filter-lists on a LandingpadInst don't make
sense.
Perhaps I'm reading your original spec wrong, perhaps I'm mis-reading
Duncan's emails, but I read them to mean that your syntax supports