James Henderson 9af6a3c5cb [yaml2obj]Allow explicit symbol indexes in relocations and emit error for bad names ... Prior to this change, the "Symbol" field of a relocation would always be assumed to be a symbol name, and if no such symbol existed, the relocation would reference index 0. This confused me when I tried to use a literal symbol index in the field: since "0x1" was not a known symbol name, the symbol index was set as 0. This change falls back to treating unknown symbol names as integers, and emits an error if the name is not found and the string is not an integer. Note that the Symbol field is optional, so if a relocation doesn't reference a symbol, it shouldn't be specified. The new error required a number of test updates. Reviewed by: grimar, ruiu Differential Revision: https://reviews.llvm.org/D58510 llvm-svn: 355938		2019-03-12 17:00:25 +00:00
..
Interpreter	[ExecutionEngine][Interpreter] Fix out-of-bounds array access.	2018-11-20 01:01:26 +00:00
MCJIT	[CMake] Use normalized Windows target triples	2018-08-09 02:16:18 +00:00
OrcLazy	[ORC] Re-apply r345077 with fixes to remove ambiguity in lookup calls.	2018-10-23 23:01:39 +00:00
OrcMCJIT	[CMake] Use normalized Windows target triples	2018-08-09 02:16:18 +00:00
RuntimeDyld	[yaml2obj]Allow explicit symbol indexes in relocations and emit error for bad names	2019-03-12 17:00:25 +00:00
2010-01-15-UndefValue.ll
fma3-jit.ll
frem.ll
lit.local.cfg
mov64zext32.ll
test-interp-vec-arithm_float.ll
test-interp-vec-arithm_int.ll
test-interp-vec-cast.ll
test-interp-vec-insertelement.ll
test-interp-vec-insertextractvalue.ll
test-interp-vec-loadstore.ll
test-interp-vec-logical.ll
test-interp-vec-select.ll
test-interp-vec-setcond-fp.ll
test-interp-vec-setcond-int.ll
test-interp-vec-shift.ll
test-interp-vec-shuffle.ll