[llvm-bugs] [Bug 44074] Add option for the behavior of __register_frame/__deregister_frame in ExecutionEngine/RuntimeDyld/RTDyldMemoryManager.cpp

via llvm-bugs llvm-bugs at lists.llvm.org
Sun Aug 15 05:41:36 PDT 2021


Harald van Dijk <harald at gigawatt.nl> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
 Fixed By Commit(s)|                            |957334382cd12ec07b46c0ddfdc
                   |                            |c220731f6d80f

--- Comment #10 from Harald van Dijk <harald at gigawatt.nl> ---
(In reply to Lang Hames from comment #9)
> Maybe the best option, since we control libunwind, would be to add a symbol
> to that that could be used to identify it at runtime (if there isn't one
> already). Then we could dynamically choose the correct behavior based on the
> presence/absence of that symbol?

If we make sure to add that symbol at the same time that we add support to
libunwind for calling __register_frame with the same arguments as libgcc's, we
could do this statically, even.

I think changing libunwind is covered by bug 47750, so we can close this one.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20210815/31bdab1c/attachment.html>

More information about the llvm-bugs mailing list