[PATCH] D39280: [libunwind] Use uint64_t for unw_word_t in ARM EHABI

mstorsjo abandoned this revision. mstorsjo added a comment. This was made obsolete by https://reviews.llvm.org/D39365. https://reviews.llvm.org/D39280 ___ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/list

[PATCH] D39280: [libunwind] Use uint64_t for unw_word_t in ARM EHABI

mstorsjo added a comment. In https://reviews.llvm.org/D39280#908825, @compnerd wrote: > I dont think that this is correct. IIRC, the unwind specification expects > `unw_word_t` to match `uintptr_t` (that is, it should be 32-bits on > https://reviews.llvm.org/P32 environments). I checked with

[PATCH] D39280: [libunwind] Use uint64_t for unw_word_t in ARM EHABI

mstorsjo added a comment. In https://reviews.llvm.org/D39280#908825, @compnerd wrote: > I dont think that this is correct. IIRC, the unwind specification expects > `unw_word_t` to match `uintptr_t` (that is, it should be 32-bits on > https://reviews.llvm.org/P32 environments). Ok, well curre

[PATCH] D39280: [libunwind] Use uint64_t for unw_word_t in ARM EHABI

compnerd added a comment. I dont think that this is correct. IIRC, the unwind specification expects `unw_word_t` to match `uintptr_t` (that is, it should be 32-bits on https://reviews.llvm.org/P32 environments). https://reviews.llvm.org/D39280 __

[PATCH] D39280: [libunwind] Use uint64_t for unw_word_t in ARM EHABI

mstorsjo created this revision. Herald added subscribers: kristof.beyls, aprantl, aemerson. This reduces the differences between the EHABI and DWARF cases. This allows getting rid of some casts in _LIBUNWIND_TRACE_API log lines, making them match what's in UnwindLevel1.c for DWARF. The only non