maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/ExecutionEngine/JITLink/X86/MachO_x86-64_ehframe.test

11 lines
449 B
Plaintext
Raw Normal View History

Revert "[JITLink] Make the JITLink MachO/x86-64 eh-frame test work on Windows." This reverts r359169, as it broke one of the windows bots. llvm-svn: 359198
2019-04-25 23:18:31 +08:00
# RUN: llvm-jitlink -noexec %S/Inputs/MachO_x86-64_ehframe.o
#
# FIXME: Produces these errors:
# JIT session error: Symbols not found: { __ZTIi, ___gxx_personality_v0 }
# llvm-jitlink.exe: Failed to materialize symbols: { biz, _main, baz }
# XFAIL: windows-msvc
Mark new jitlink test XFAIL for windows llvm-svn: 359151
2019-04-25 07:11:17 +08:00
#
[JITLink] Refer to FDE's CIE (not the most recent CIE) when parsing eh-frame. Frame Descriptor Entries (FDEs) have a pointer back to a Common Information Entry (CIE) that describes how the rest FDE should be parsed. JITLink had been assuming that FDEs always referred to the most recent CIE encountered, but the spec allows them to point back to any previously encountered CIE. This patch fixes JITLink to look up the correct CIE for the FDE. The testcase is a MachO binary with an FDE that refers to a CIE that is not the one immediately proceeding it (the layout can be viewed wit 'dwarfdump --eh-frame <testcase>'. This test case had to be a binary as llvm-mc now sorts FDEs (as of r356216) to ensure FDEs *do* point to the most recent CIE. llvm-svn: 359105
2019-04-24 23:15:55 +08:00
# Perform a no-exec link of MachO_x86-64_ehframe and verify that it does not
# generate any errors despite the last FDE referring to the first CIE (rather
Mark new jitlink test XFAIL for windows llvm-svn: 359151
2019-04-25 07:11:17 +08:00
# than the most recent).