[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160122190940.GJ4034@kernel.org>
Date: Fri, 22 Jan 2016 16:09:40 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Daniel Borkmann <daniel@...earbox.net>
Cc: Adam Jackson <ajax@...hat.com>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Wang Nan <wangnan0@...wei.com>, ast@...nel.org,
linux-kernel@...r.kernel.org, Li Zefan <lizefan@...wei.com>,
pi3orama@....com, Dave Airlie <airlied@...hat.com>
Subject: Re: clang --target=bpf missing on f23 was: Re: [PATCH 1/2] perf
test: Add libbpf relocation checker
Em Fri, Jan 22, 2016 at 06:56:02PM +0100, Daniel Borkmann escreveu:
> On 01/22/2016 06:35 PM, Adam Jackson wrote:
> >On Fri, 2016-01-22 at 14:22 -0300, Arnaldo Carvalho de Melo wrote:
> >
> >> the 'bpf' target for clang is being used together with perf to
> >>build scriptlets into object code that then gets uploaded to the kernel
> >>via sys_bpf(), was the decision not to include 'bpf' just an accident?
> >
> >I wouldn't call it a "decision", that would imply intent. The main
> >reason I explicitly list targets for llvm is to limit the CPU backends
> >to arches Fedora actually runs on (which itself is because I really
> >only care about llvmpipe, and am only touching llvm because it's in my
> >way). Had no idea there was a bpf backend, so never thought to enable
> >it.
> >
> >llvm-3.7.0-4.fc2{3,4} are building now with the bpf backend enabled,
> >I'll create an update for F23 when it's built.
>
> Awesome, thanks!
Seconded, thanks for the fast response and for adding the bpf target!
Now that is a good, intentional decision 8-)
- Arnaldo
Powered by blists - more mailing lists