llvm dev - Nov 2018 - [DWARF] Why epilogue_begin was not emitted?

We'll be adding this (OpenVMS needs to know about epilogue boundaries to
handle asynchronous exceptions in an epilogue).  We are currently
out-of-tree but will be rebasing next year and will then offer up what
we have done.

Epilogue support was attempted at some point, but Francis told me that
it had problems with shrink-wrapping (I think that was the reason).

John

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181129/90374391/attachment.sig>

> On 29 Nov 2018, at 19:53, John Reagan via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> We'll be adding this (OpenVMS needs to know about epilogue boundaries
to
> handle asynchronous exceptions in an epilogue).  We are currently
> out-of-tree but will be rebasing next year and will then offer up what
> we have done.
> 
> Epilogue support was attempted at some point, but Francis told me that
> it had problems with shrink-wrapping (I think that was the reason).
I might be wrong but I think I was mentioning adding CFI emission support in
epilogues, which should be working on X86: https://reviews.llvm.org/rL330706
<https://reviews.llvm.org/rL330706>.

Cheers,

— 
Francis
> 
> John
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181129/a119f2e4/attachment.html>