<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:rnk@google.com" title="Reid Kleckner <rnk@google.com>"> <span class="fn">Reid Kleckner</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - ClangCl: windows structured exception handling crash at the runtime"
href="https://bugs.llvm.org/show_bug.cgi?id=44372">bug 44372</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>DUPLICATE
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>rnk@google.com
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - ClangCl: windows structured exception handling crash at the runtime"
href="https://bugs.llvm.org/show_bug.cgi?id=44372#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - ClangCl: windows structured exception handling crash at the runtime"
href="https://bugs.llvm.org/show_bug.cgi?id=44372">bug 44372</a>
from <span class="vcard"><a class="email" href="mailto:rnk@google.com" title="Reid Kleckner <rnk@google.com>"> <span class="fn">Reid Kleckner</span></a>
</span></b>
<pre>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:
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - A range of ScopeRecord does not match the code enclosed by __try"
href="show_bug.cgi?id=44174#c1">https://bugs.llvm.org/show_bug.cgi?id=44174#c1</a>
Pasted below:
"""
This is currently working-as-designed, and documented:
<a href="https://clang.llvm.org/docs/MSVCCompatibility.html">https://clang.llvm.org/docs/MSVCCompatibility.html</a>
"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:
<a href="http://lists.llvm.org/pipermail/llvm-dev/2019-November/136701.html">http://lists.llvm.org/pipermail/llvm-dev/2019-November/136701.html</a>
"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 <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Add support for asynchronous "non-call" exceptions, eliminate invoke/call dichotomy"
href="show_bug.cgi?id=1269">bug 1269</a> ***</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>