https://bugs.llvm.org/show_bug.cgi?id=44074
Harald van Dijk <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Fixed By Commit(s)| |957334382cd12ec07b46c0ddfdc
| |c220731f6d80f
--- Comment #10 from Harald van Dijk <[email protected]> ---
(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._______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
