From: Andrew Lunn <andrew@lunn.ch>
To: Shubham Bansal <illusionist.neo@gmail.com>
Cc: linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] RFC: arm: eBPF JIT compiler
Date: Tue, 23 May 2017 22:46:08 +0200 [thread overview]
Message-ID: <20170523204608.GG24807@lunn.ch> (raw)
In-Reply-To: <1495564433-9750-1-git-send-email-illusionist.neo@gmail.com>
On Wed, May 24, 2017 at 12:03:53AM +0530, Shubham Bansal wrote:
> The JIT compiler emits ARM 32 bit instructions. Currently, It supports
> eBPF only. Classic BPF is supported because of the conversion by BPF
> core.
make mvebu_v5_defconfig
make -s -j 16
arch/arm/net/bpf_jit_32.c: In function emit_rev16:
arch/arm/net/bpf_jit_32.c:1019:7: error: implicit declaration of function ARM_MOV_S [-Werror=implicit-function-declaration]
emit(ARM_MOV_S(tmp2[0], rn, SRTYPE_LSR, 8), ctx);
^~~~~~~~~
arch/arm/net/bpf_jit_32.c: In function emit_rev32:
arch/arm/net/bpf_jit_32.c:1037:36: error: macro "ARM_MOV_I" passed 3 arguments, but takes just 2
emit(ARM_MOV_I(tmp2[1], rn, 0xff00), ctx);
^
arch/arm/net/bpf_jit_32.c:1037:7: error: ARM_MOV_I undeclared (first use in this function)
emit(ARM_MOV_I(tmp2[1], rn, 0xff00), ctx);
^~~~~~~~~
arch/arm/net/bpf_jit_32.c:1037:7: note: each undeclared identifier is reported only once for each function it appears in
arch/arm/net/bpf_jit_32.c:1039:41: error: macro "ARM_MOV_I" passed 3 arguments, but takes just 2
emit(ARM_MOV_I(tmp2[0], tmp2[0], 0xff00), ctx);
^
arch/arm/net/bpf_jit_32.c: In function build_insn:
arch/arm/net/bpf_jit_32.c:1393:30: error: macro "ARM_AND_R" requires 3 arguments, but only 2 given
emit(ARM_AND_R(rt, tmp2[1]), ctx);
^
arch/arm/net/bpf_jit_32.c:1393:9: error: ARM_AND_R undeclared (first use in this function)
emit(ARM_AND_R(rt, tmp2[1]), ctx);
Andrew
next prev parent reply other threads:[~2017-05-23 20:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 18:33 [PATCH] RFC: arm: eBPF JIT compiler Shubham Bansal
2017-05-23 19:00 ` Russell King - ARM Linux
2017-05-23 19:13 ` Shubham Bansal
2017-05-23 20:34 ` Andrew Lunn
2017-05-23 20:46 ` Andrew Lunn [this message]
2017-05-23 20:54 ` Shubham Bansal
2017-05-23 23:25 ` Andrew Lunn
2017-05-24 20:31 ` Shubham Bansal
2017-05-25 16:12 ` Shubham Bansal
2017-05-25 17:00 ` Andrew Lunn
2017-05-25 17:22 ` Andrew Lunn
[not found] ` <CAHgaXd+CVrDEA=E2=23Qp6wk50=dBnFS6TiCtvphTBMjUywrGg@mail.gmail.com>
2017-05-25 18:28 ` Andrew Lunn
2017-05-25 18:35 ` Shubham Bansal
2017-05-25 18:48 ` Andrew Lunn
2017-05-25 19:09 ` Shubham Bansal
2017-05-25 19:44 ` Florian Fainelli
2017-05-25 20:08 ` Shubham Bansal
2017-05-25 20:59 ` Kees Cook
2017-05-25 21:12 ` Florian Fainelli
2017-05-25 22:10 ` Russell King - ARM Linux
2017-05-23 21:17 ` Shubham Bansal
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=20170523204608.GG24807@lunn.ch \
--to=andrew@lunn.ch \
--cc=illusionist.neo@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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