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. > > Also, the BPF loaders in the kernel do not execute .ini/.fini > constructors/destructors. Therefore, this patch provides empty crtn.S > and cri.S files. > > libgcc/ChangeLog: > > * config.host: Set cpu_type for bpf-*-* targets. > * config/bpf/t-bpf: Likewise. > * config/bpf/crtn.S: Likewise. > * config/bpf/crti.S: New file.
> diff --git a/libgcc/config/bpf/crti.S b/libgcc/config/bpf/crti.S > new file mode 100644 > index 00000000000..e69de29bb2d > diff --git a/libgcc/config/bpf/crtn.S b/libgcc/config/bpf/crtn.S > new file mode 100644 > index 00000000000..e69de29bb2d > diff --git a/libgcc/config/bpf/t-bpf b/libgcc/config/bpf/t-bpf > new file mode 100644 > index 00000000000..c1bda7c98cb > --- /dev/null > +++ 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. Jeff
