> On Thu, Feb 24, 2022 at 2:49 PM Jose E. Marchesi
> wrote:
>>
>>
>> > On Wed, Feb 23, 2022 at 8:56 PM Jose E. Marchesi
>> > wrote:
>> >>
>> >> This patch changes the build machinery in order to disable the build
>> >> of GCOV (both compiler and libgcc) in bpf-*-* targets. The reason for
>> >>
On Thu, Feb 24, 2022 at 2:49 PM Jose E. Marchesi
wrote:
>
>
> > On Wed, Feb 23, 2022 at 8:56 PM Jose E. Marchesi
> > wrote:
> >>
> >> This patch changes the build machinery in order to disable the build
> >> of GCOV (both compiler and libgcc) in bpf-*-* targets. The reason for
> >> this change i
> On Wed, Feb 23, 2022 at 8:56 PM Jose E. Marchesi
> wrote:
>>
>> This patch changes the build machinery in order to disable the build
>> of GCOV (both compiler and libgcc) in bpf-*-* targets. The reason for
>> this change is that BPF is (currently) too restricted in order to
>> support the cov
On Wed, Feb 23, 2022 at 8:56 PM Jose E. Marchesi
wrote:
>
> This patch changes the build machinery in order to disable the build
> of GCOV (both compiler and libgcc) in bpf-*-* targets. The reason for
> this change is that BPF is (currently) too restricted in order to
> support the coverage instr
This patch changes the build machinery in order to disable the build
of GCOV (both compiler and libgcc) in bpf-*-* targets. The reason for
this change is that BPF is (currently) too restricted in order to
support the coverage instrumentalization.
Tested in bpf-unknown-none and x86_64-linux-gnu ta
