<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We would like to upstream exception handling support for Windows on ARM64. Microsoft-published specifications can be found here:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>a) https://docs.microsoft.com/en-us/cpp/build/arm64-exception-handling<o:p></o:p></p><p class=MsoNormal>b) https://docs.microsoft.com/en-us/cpp/build/arm64-windows-abi-conventions<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We propose the following approach:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1) Upstream miscellaneous clang and llvm patches that are needed for exception handling on ARM64 Windows. These are small patches that deal with the ABI, relocations, etc. There are around 8 or 9 patches to upstream.<o:p></o:p></p><p class=MsoNormal>2) Upstream the MCLayer part. This mostly deals with unwinding opcodes that are described in a). This will probably consist of two patches.<o:p></o:p></p><p class=MsoNormal>3) Upstream the AArch64 frame lowering part. This mostly deals with emitting unwinding opcodes, as well as some small changes to the exception handling tables. Probably two patches.<o:p></o:p></p><p class=MsoNormal>4) Upstream setjmp support. This consists of two patches (one clang and one llvm).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Any thoughts?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Mandeep and I will start upstreaming shortly.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Sanjin<o:p></o:p></p></div></body></html>