Renato Golin
2011-Jun-13 21:37 UTC
[LLVMdev] Is LLVM expressive enough to represent asynchronous exceptions?
On 13 June 2011 22:27, John McCall <rjmccall at apple.com> wrote:> But yes, I am not inclined to support asynchronous exceptions from signals.Ah, ok. I was beginning to wonder... ;) --renato
Bill Wendling
2011-Jun-14 01:03 UTC
[LLVMdev] Is LLVM expressive enough to represent asynchronous exceptions?
On Jun 13, 2011, at 2:37 PM, Renato Golin wrote:> On 13 June 2011 22:27, John McCall <rjmccall at apple.com> wrote: >> But yes, I am not inclined to support asynchronous exceptions from signals. > > Ah, ok. I was beginning to wonder... ;) >You laugh, but we support it (or at least we did at one point with gcc-4.2). -bw
Renato Golin
2011-Jun-14 08:37 UTC
[LLVMdev] Is LLVM expressive enough to represent asynchronous exceptions?
On 14 June 2011 02:03, Bill Wendling <wendling at apple.com> wrote:> You laugh, but we support it (or at least we did at one point with gcc-4.2).In IR? In the form of synchronous exceptions? How can you possible represent a "signal cfg" in IR? Is there a need for unwinding information at all? cheers, --renato
Seemingly Similar Threads
- [LLVMdev] Is LLVM expressive enough to represent asynchronous exceptions?
- [LLVMdev] Is LLVM expressive enough to represent asynchronous exceptions?
- [LLVMdev] Is LLVM expressive enough to represent asynchronous exceptions?
- [LLVMdev] Is LLVM expressive enough to represent asynchronous exceptions?
- [LLVMdev] Is LLVM expressive enough to represent asynchronous exceptions?