Displaying 2 results from an estimated 2 matches for "reg31".
Did you mean:
reg1
2016 Jan 20
2
Getting _eh_frame parser for llvm
...and I haven’t yet been able to find the cause of the issue.
Igor, the failures I saw on a number of bots were complaining about one of the CHECK lines in the test case (test/tools/llvm-objdump/eh_frame-arm64.test)I adapted in the given review.
The line in question was:
# CHECK: DW_CFA_def_cfa: reg31 +0
but the bots complained saying that there was no 'DW_CFA_def_cfa: reg31 +0’ but there was a 'DW_CFA_def_cfa: reg0 +31’.
That led me to thinking there was an endian issue and that different bots were reading either 0 or 31 in the different parts of this instruction.
Unfortunately, that...
2016 Jan 20
2
Getting _eh_frame parser for llvm
> On 20 January 2016 at 09:21, Igor Laevsky via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> Hi all,
>>
>> Not so long ago we have found ourselves in need of a robust _eh_frame parser. All we wanted is the ability to parse .eh_frame section emitted by LLVM's MCJIT. Considering this, LLVM would be a natural place for implementing such parser.
>>