Hi Jeff.
First of all, thanks for reviewing the port.
> +++ b/libgcc/config/bpf/t-bpf
> @@ -0,0 +1,24 @@
> +HOST_LIBGCC2_CFLAGS += -O0
> +LIB2ADDEH =
I'd like to understand the motivation behind the -O0, but otherwise I
don't see anything particularly concerning here.
O
On 8/16/19 6:50 PM, Jose E. Marchesi wrote:
> This patch adds an eBPF port to libgcc.
>
> As of today, compiled eBPF programs do not support a single-entry
> point schema. Instead, a BPF "executable" is a relocatable ELF object
> file containing multiple entry points, in certain named sections.
>
This patch adds an eBPF port to libgcc.
As of today, compiled eBPF programs do not support a single-entry
point schema. Instead, a BPF "executable" is a relocatable ELF object
file containing multiple entry points, in certain named sections.
Also, the BPF loaders in the kernel do not execute .in
