From: Aaron Conole <aconole@bytheb.org>
To: David Miller <davem@davemloft.net>
Cc: ast@fb.com, daniel@iogearbox.net, netdev@vger.kernel.org,
xdp-newbies@vger.kernel.org
Subject: Re: [PATCH v4 binutils] Add BPF support to binutils...
Date: Mon, 01 May 2017 14:39:39 -0400 [thread overview]
Message-ID: <f7t37coxvys.fsf@redhat.com> (raw)
In-Reply-To: <20170501.135202.2175412915689459473.davem@davemloft.net> (David Miller's message of "Mon, 01 May 2017 13:52:02 -0400 (EDT)")
David Miller <davem@davemloft.net> writes:
> From: Aaron Conole <aconole@bytheb.org>
> Date: Mon, 01 May 2017 13:22:00 -0400
>
>> x86-64:
>> Running /home/aconole/git/binutils-gdb/gas/testsuite/gas/bpf/bpf.exp ...
>> FAIL: jump
>> FAIL: call
>> FAIL: imm64a
>> Running /home/aconole/git/binutils-gdb/gas/testsuite/gas/cfi/cfi.exp ...
>
> I cannot reproduce this, can you show what it says in the:
>
> /home/aconole/git/binutils-gdb/gas/testsuite/gas.log
>
> file near the "FAIL" cases?
Executing on host: sh -c {/home/aconole/git/binutils-gdb/gas/testsuite/../../binutils/objdump -dr dump.o >dump.out 2>gas.stderr} /dev/null (timeout = 300)
spawn [open ...]
regexp_diff match failure
regexp "^ 108: 95 00 00 00 00 00 00 00 exit$"
line " 108: 95 00 00 00 00 00 00 00 exit "
FAIL: jump
Same style of error for call and imm64a. After reverting and then
re-applying your patch, the FAILs all go away, so I must have broken
these files somehow. Sorry for the false alarm.
-Aaron
next prev parent reply other threads:[~2017-05-01 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 16:07 [PATCH v4 binutils] Add BPF support to binutils David Miller
2017-05-01 17:22 ` Aaron Conole
2017-05-01 17:42 ` David Miller
2017-05-01 17:52 ` David Miller
2017-05-01 18:39 ` Aaron Conole [this message]
2017-05-01 18:50 ` David Miller
2017-05-02 3:49 ` Alexei Starovoitov
2017-05-02 3:51 ` David Miller
2017-05-05 19:43 ` David Miller
2017-05-05 18:24 ` Alexei Starovoitov
2017-05-05 18:53 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7t37coxvys.fsf@redhat.com \
--to=aconole@bytheb.org \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=xdp-newbies@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).