<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 29 Nov 2018, at 19:53, John Reagan via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">We'll be adding this (OpenVMS needs to know about epilogue boundaries to<br class="">handle asynchronous exceptions in an epilogue). We are currently<br class="">out-of-tree but will be rebasing next year and will then offer up what<br class="">we have done.<br class=""><br class="">Epilogue support was attempted at some point, but Francis told me that<br class="">it had problems with shrink-wrapping (I think that was the reason).<br class=""></div></div></blockquote><div><br class=""></div><div>I might be wrong but I think I was mentioning adding CFI emission support in epilogues, which should be working on X86: <a href="https://reviews.llvm.org/rL330706" class="">https://reviews.llvm.org/rL330706</a>.</div><div><br class=""></div><div>Cheers,</div><div><br class=""></div><div>— </div><div>Francis</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">John<br class=""><br class="">_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></div></blockquote></div><br class=""></body></html>