search for: call_addr

...> > 0x42: bar: > 0x42: retq > 0x43: foo: > 0x43: callq 0x42 > 0x44: inst1: > 0x44: retq > > And the FileCheck equivalent of > > # rtdyld-check: *{4}(inst1 - 4) = (bar - inst1) & 0xffffffff > > would be something like: > > CHECK: [[CALL_ADDR:.*]]: bar: > CHECK: callq [[CALL_ADDR]] > > Which, I suppose, depends on disassembler working correctly, not sure > if that's high risk/complicated. > > Alternatively - could llvm-rtdyld just print a simple description of > relocations its applied and the location of sym...

Hi Everyone, For your consideration: A proposal to improve regression test support for RuntimeDyld. Short version: We can make RuntimeDyld far more testable by adding a trivial pointer-expression language that allows us to describe how memory should look post-relocation. Jump down to "The Proposal" for details. Long version: Background: For those unfamiliar with it, RuntimeDyld a