[llvm-bugs] [Bug 44372] ClangCl: windows structured exception handling crash at the runtime

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=44372

Reid Kleckner <rnk at google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
                 CC|                            |rnk at google.com
             Status|NEW                         |RESOLVED

--- Comment #1 from Reid Kleckner <rnk at google.com> ---
This is a non-call exception, which LLVM cannot catch in the same frame. This
is working-as-designed. I recently wrote up the current the state here:
https://bugs.llvm.org/show_bug.cgi?id=44174#c1

Pasted below:
"""
This is currently working-as-designed, and documented:
https://clang.llvm.org/docs/MSVCCompatibility.html
"Asynchronous Exceptions (SEH): Partial. Structured exceptions (__try /
__except / __finally) mostly work on x86 and x64. LLVM does not model
asynchronous exceptions, so it is currently impossible to catch an asynchronous
exception generated in the same frame as the catching __try."

It was brought up recently and (hopefully) clarified here:
http://lists.llvm.org/pipermail/llvm-dev/2019-November/136701.html
"the important thing to understand is that LLVM is currently incapable of
representing non-call instructions that might throw an exception."

There may be some future effort to implement support for non-call exceptions,
but to my knowledge, nobody has started and there is no timeline.
"""

*** This bug has been marked as a duplicate of bug 1269 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20191224/90e8af65/attachment.html>