<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Issue</th>
<td>
<a href=https://github.com/llvm/llvm-project/issues/150057>150057</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>
Follow-on work for IP2State table improvements
</td>
</tr>
<tr>
<th>Labels</th>
<td>
new issue
</td>
</tr>
<tr>
<th>Assignees</th>
<td>
</td>
</tr>
<tr>
<th>Reporter</th>
<td>
sivadeilra
</td>
</tr>
</table>
<pre>
As requested in review for #144745, this issue tracks further improvements for how exception-handling tables for Windows are handled on AMD64.
Specifically:
* Can NOP padding be avoided in more situations? There is some discussion of whether UEFI should or should not use NOP padding.
* Can we use INT3 instead of NOP when we know that a CALL is for a no-return function? This information is a little harder to get at the MachineFunction level, so it may require propagating more information.
* Can we avoid NOP padding when a CALL is before an SEH epilogue but the CALL is within a null region? Null regions don't require any cleanup, so the NOP can be avoided.
</pre>
<img width="1" height="1" alt="" src="http://email.email.llvm.org/o/eJxcU8Fy4zYM_RrqgrFHoqw4OujgZlfTzOymO5Pt9AyJsMiGIlUStJq_71B2mmRPtgTg4b0HPYzRTI6oE81vovlSYGLtQxfNBRUZG7AYvHrtThEC_ZMoMikwDgJdDK1w9gGErKvD4XhohHwA1iaCiTERcMDxJcI5BdYUwMxL8BeayXHc5rRfgf4daWHj3U6jU9a4CRgHS9eOv4xTfo2AgWCrkwLv4PT9y91hL8qTKE_PC43mbEa09lXUp-tLIU_wgA6e_vgBCyqVYQcCvHijrvRnHwii4YR5eRR1D_BTUyAwEaKfCZSJY4rReAf-DKumTcSfX_tHiNonq8CHt3_OM6RIH_ftP9BYaas-Pv2swbjIhCpj5u5V01Z_cX4F1siA8HD69i3TyA4gOL8LxCk4OCc3ZrY3stlnd_Zh3iTkAQRrmG32KigKwB4mYkAG1gTfcdTGUX9DAUsXsvlk0YNhmPF1u7AJBEvwC07I2bfNqQ-LfhG2efrJ6E3Su4qBzhkBHTx__R1oMdZPiWBIV1ZvbathbfKcS9ZCoOlN6NP7cwTlnZBH_p8oulcYLaFLy01JxsxsRnQfTp5JF6qrVVu3WFBXHZtallV7KAvdNfV9Uw5jO5btcKRzO9y3KIdjQ01bomqbwnSylE15lLK6q2XV7ulYNeqeWqrK6q6q7sShpBmN3Vt7mfc-TMWWgK5qyrI5FhYHsnELmJSO1ms-hJQ5b6HLQ7shTVEcSmsix3cYNmyp6721ft15B6sPL9t38fhDPjMyXdPyKVtFCrbTzEvMeZC9kP1kWKdhP_pZyD6D3352S_B_08hC9hulKGR_43zp5H8BAAD___B6YmM">