search for: exception_point

Displaying 7 results from an estimated 7 matches for "exception_point".

Did you mean: exception_pointer
2010 Sep 27
1
[LLVMdev] LLVM Exception Handling
On 27 September 2010 01:12, Nathan Jeffords <blunted2night at gmail.com> wrote: > How about this syntax: > invoke @method(i32 %arg) >   ret i32 %return_value to label %success_branch > unwind i8* %exception_pointer to label %error_branch > this makes the instruction self consistent, and self documenting I like it. What if the function returns void? Would you omit the whole type+value? -- cheers, --renato http://systemcall.org/ Reclaim your digital rights, eliminate DRM, learn more at http://www.def...
2010 Sep 26
2
[LLVMdev] LLVM Exception Handling
Ok, I see it. Works for me. On Sun, Sep 26, 2010 at 3:01 PM, Renato Golin <rengolin at systemcall.org>wrote: > On 26 September 2010 22:11, Nathan Jeffords <blunted2night at gmail.com> > wrote: > > The "exception" value will *always* be i8*, it is not possible for it to > be > > anything different. > > In the end, this a minor parser detail and it
2010 Sep 27
0
[LLVMdev] LLVM Exception Handling
How about this syntax: invoke @method(i32 %arg) ret i32 %return_value to label %success_branch unwind i8* %exception_pointer to label %error_branch this makes the instruction self consistent, and self documenting -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100926/5de04087/attachment.html>
2014 Mar 15
2
PATCH: OS SSE support detection, version 2
Erik de Castro Lopo wrote: >> About part 1:does it have any problems? I can split it into several patches >> (1 fix = 1 patch) or explain the changes in it in detail. > > I didn't apply patch1 because I mis-read your comment here: > > http://lists.xiph.org/pipermail/flac-dev/2014-March/004582.html > > So, for the patches in this email: > >
2014 Nov 10
2
[LLVMdev] RFC: How to represent SEH (__try / __except) in LLVM IR
...to i8*) > store i32 0, i32* %r, align 4 > br label %__try.cont > > __try.cont: ; preds = %__except, > %entry > %2 = load i32* %r, align 4 > ret i32 %2 > } > > define internal i32 @"\01?filt$0 at 0@safe_div@@"(i8* %exception_pointers, > i8* %frame_pointer) { > entry: > %0 = bitcast i8* %exception_pointers to i32** > %1 = load i32** %0, align 8 > %2 = load i32* %1, align 4 > %cmp = icmp eq i32 %2, -1073741676 > %conv = zext i1 %cmp to i32 > ret i32 %conv > } > > declare i32 @__C_sp...
2001 Jul 11
1
Porting MS Structured Exception Handling to Linux.
...to port some more code from windows 2000 to linux. The specific functionality I would like to port is called "Structured Exception Handling" and it works like so: 1. Define a function which based upons a signal throws an exceptoion. For example: void translateException(unsigned int u, EXCEPTION_POINTERS* pExp) { switch (u) { case (unsigned int)0xc0000005: throw AccessViolationException("SE_Exception::translateException() - u == 0xc0000005", pExp, u); break; default: throw SE_Exception("SE_Exception::translateException() - default:", pExp, u ); } } The id...
2014 Nov 13
2
[LLVMdev] RFC: How to represent SEH (__try / __except) in LLVM IR
..., i8*)* @"\01?filt$0 at 0@safe_div@@" to i8*) store i32 0, i32* %r, align 4 br label %__try.cont __try.cont: ; preds = %__except, %entry %2 = load i32* %r, align 4 ret i32 %2 } define internal i32 @"\01?filt$0 at 0@safe_div@@"(i8* %exception_pointers, i8* %frame_pointer) { entry: %0 = bitcast i8* %exception_pointers to i32** %1 = load i32** %0, align 8 %2 = load i32* %1, align 4 %cmp = icmp eq i32 %2, -1073741676 %conv = zext i1 %cmp to i32 ret i32 %conv } declare i32 @__C_specific_handler(...) -------------- next part ------...