[LLVMdev] Is LLVM expressive enough to represent asynchronous exceptions?

[Chris Lattner]

On Jun 13, 2011, at 3:15 PM, Jakob Stoklund Olesen wrote:

> 
> On Jun 13, 2011, at 2:52 PM, Chris Lattner wrote:
> 
>> Synchronous exceptions like divide by zero or null pointer derefs are another thing entirely though.
> 
> When runtimes support this, do they preserve all registers or just the non-volatile registers, like a normal unwinder? How is information about the exception passed to the landing pad?

The idea is that each of these potentially trapping synchronous operations needs to be treated as a potential control flow operation, just like "invoke" is to "call".

-Chris