Note that there is a triple indirection involved with personalities and compact unwind: 1. Two bits of each CU encoding are used as an offset into the personality array. 2. Each entry of the personality array is an offset from the image base. The resulting address (after adding the image base) should point within the GOT. 3. The corresponding GOT entry contains the actual pointer to the personality function. To further complicate things, when the personality function is in the object file (as opposed to a dylib), its references in `__compact_unwind` may refer to it via a section + offset relocation instead of a symbol relocation. Since our GOT implementation can only create entries for symbols, we have to create a synthetic symbol at the given section offset. Reviewed By: clayborg Differential Revision: https://reviews.llvm.org/D95809
22 lines
851 B
Plaintext
22 lines
851 B
Plaintext
# REQUIRES: x86
|
|
|
|
# FIXME(gkm): This test is fast on a Release tree, and slow (~10s) on
|
|
# a Debug tree mostly because of llvm-mc. Is there a way to prefer the
|
|
# fast installed llvm-mc rather than the slow one in our Debug tree?
|
|
|
|
# If headers and offsets are proper, then ...
|
|
#
|
|
# 1) llvm-objdump will not crash, and exit with good status
|
|
#
|
|
# 2) Summary encodings from the input object will match
|
|
# those from the linked output
|
|
#
|
|
# 3) Encodings & symbols from the intput object will match
|
|
# those from the linked output
|
|
|
|
# RUN: %python %S/tools/generate-cfi-funcs.py --seed=johnnyapple >%t.s
|
|
# RUN: llvm-mc -filetype=obj -triple=x86_64-apple-darwin19.0.0 -o %t.o %t.s
|
|
# RUN: %lld -Z -L%S/Inputs/MacOSX.sdk/usr/lib -lSystem -o %t %t.o
|
|
# RUN: llvm-objdump --unwind-info --syms %t %t.o >%t.dump
|
|
# RUN: %python %S/tools/validate-unwind-info.py %t.dump
|