On Mon, Jun 20, 2016 at 10:32 AM, Alexei Starovoitov < [email protected]> wrote:
> On Mon, Jun 20, 2016 at 10:17 AM, Richard Henderson via iovisor-dev > <[email protected]> wrote: > > Well, that was quick. > > thanks! > > > Would someone from the iovisor project like to be the official contact > for > > this? Otherwise I'll give them contact details for Red Hat. > > can probably put my name or something generic like 'BPF developers'. > and [email protected] as an email. > If you can leave the phone number empty that's the easiest. > Brenden, any suggestions? > I don't think we have a generic phone number to give, but the usage of iovisor-dev mailer sounds appropriate to me. Is there a precedent of using an alias already? > > -------- Forwarded Message -------- > > Subject: Re: Request ELF e_machine number for Linux BPF > > Date: Mon, 20 Jun 2016 18:15:49 +0200 > > From: Michael.Brinke-Engel <[email protected]> > > To: Richard Henderson <[email protected]>, [email protected], > > [email protected] > > > > > > > > Hi RIchard, > > > > Thanks for your request. > > > > The following values for your request will be added to the web document > of > > gABI: > > > > EM_BPF 247 Linux BPF – in-kernel virtual machine > > > > Can you please let me have the necessary details for the official contact > > with regard to this entry: > > > > *Contact info for EM_BPF* > > > > * Name ??? > > * Phone ??? > > * E-mail ??? > > > > > > Regards, > > > > Michael Brinke-Engel > > > > --- > > > > Am 16.06.2016 um 22:54 schrieb Richard Henderson: > > > >> The Linux kernel supports a virtual machine derived from the Berkeley > >> Packet > >> Filter (BPF) virtual machine. LLVM has a compiler backend targeting > this > >> virtual machine, which produces ELF object files. > >> > >> Currently, the LLVM backend is using EM_NONE, which is less than optimal > >> for > >> the rest of the compiler tool chain. > >> > >> We request an official number for the symbolic name EM_BPF, so as to > >> improve > >> this situation. > >> > >> Thanks, > >> > >> > >> r~ > > > > > > _______________________________________________ > > iovisor-dev mailing list > > [email protected] > > https://lists.iovisor.org/mailman/listinfo/iovisor-dev >
_______________________________________________ iovisor-dev mailing list [email protected] https://lists.iovisor.org/mailman/listinfo/iovisor-dev
