Displaying 3 results from an estimated 3 matches for "0_9".
Did you mean:
09
2010 Dec 03
1
[LLVMdev] Alternative exception handling proposal
..._ZTIPSt9exception to i8*))
%2 = icmp eq i32 %filter, %typeid
br i1 %2, label %"<L3>", label %rewind
"<L3>": ; preds = %"<L2>"
%D.2320_8 = tail call i8* @__cxa_begin_catch(i8* %exc_ptr) nounwind
%e.0_9 = bitcast i8* %D.2320_8 to %struct.exception*
%D.2312_11 = tail call i8* @__cxa_allocate_exception(i64 8) nounwind
%D.2321_12 = bitcast i8* %D.2312_11 to %struct.exception**
store %struct.exception* %e.0_9, %struct.exception** %D.2321_12, align 8
invoke void @__cxa_throw(i8* %D.2312_11,...
2010 Dec 02
0
[LLVMdev] Alternative exception handling proposal
On Dec 2, 2010, at 2:21 AM, Duncan Sands wrote:
> Hi Bill,
>
>> This is similar to my first proposal.
>
> yup, I still consider your first proposal to have been basically sound.
>
> But it also suffers from a major problem,
>> which stopped that proposal dead in its tracks. Namely, you have information in
>> one place which needs to be shared in two
2010 Dec 02
3
[LLVMdev] Alternative exception handling proposal
Hi Bill,
> This is similar to my first proposal.
yup, I still consider your first proposal to have been basically sound.
But it also suffers from a major problem,
> which stopped that proposal dead in its tracks. Namely, you have information in
> one place which needs to be shared in two different, but possibly disjoint,
> places: the type, filters, and personality information. In