On 4/28/17 9:38 AM, David Miller wrote:
From: Alexei Starovoitov
Date: Fri, 28 Apr 2017 09:22:32 -0700
On 4/28/17 9:17 AM, David Miller wrote:
Even if I give it -triple=bpfeb it emits immediates incorrectly.
The bug is certainly in the insn field fetcher of the disassembler.
got it. so the
From: Alexei Starovoitov
Date: Fri, 28 Apr 2017 09:22:32 -0700
> On 4/28/17 9:17 AM, David Miller wrote:
>> Even if I give it -triple=bpfeb it emits immediates incorrectly.
>>
>> The bug is certainly in the insn field fetcher of the disassembler.
>
> got it. so the binary looks correct, but disa
On 4/28/17 9:17 AM, David Miller wrote:
Even if I give it -triple=bpfeb it emits immediates incorrectly.
The bug is certainly in the insn field fetcher of the disassembler.
got it. so the binary looks correct, but disasm output is wrong?
Thanks! Looks like there is a bug there indeed.
From: Alexei Starovoitov
Date: Tue, 25 Apr 2017 20:48:52 -0700
> On 4/25/17 10:13 AM, David Miller wrote:
>>
>> I think there are some endianness issues ;-)
>>
>> davem@patience:~/src/GIT/net-next/tools/testing/selftests/bpf$
>> llvm-objdump -S x.o
>
> nice host name ;)
>
>> x.o:file format
On 4/25/17 10:13 AM, David Miller wrote:
I think there are some endianness issues ;-)
davem@patience:~/src/GIT/net-next/tools/testing/selftests/bpf$ llvm-objdump -S
x.o
nice host name ;)
x.o:file format ELF64-BPF
Disassembly of section test1:
process:
0: b7 00 00 00 00 00
