[LLVMdev] RFC: Native Windows C++ exception handling

[Reid Kleckner]

On Fri, Feb 13, 2015 at 7:11 AM, Joseph Tremoulet <jotrem at microsoft.com>
wrote:

>  Yes, it seems like WinEHPrepare should always be able to move landing
> pad code to somewhere appropriate.  Even if there's some involved code to
> handle the cases that force #1, it's great that the complexity is contained
> in WinEHPrepare.
>
>
>
> I'm still confused about the apparent lack of constraints after
> WinEHPrepare.  *Can we simply require/assume that WinEHPrepare be run
> after any passes that may move/insert code into landing pads?  Is that
> documented somewhere?*
>

Yeah, this is kind of fuzzy. EH preparation just happens very late, after
all the interesting passes (sroa, inlining, etc) have run. There are some
passes that run afterwards, but they are typically lowering passes, and
won't do this kind of hoisting.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150213/49d36ca0/attachment.html>