Re: [PATCH bpf-next 1/2] libbpf: Do not use btf_dump__new macro for c++ objects

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Dec 23, 2021 at 8:13 AM Yonghong Song <yhs@xxxxxx> wrote:
>
>
>
> On 12/23/21 5:17 AM, Jiri Olsa wrote:
> > As reported in here [0], C++ compilers don't support __builtin_types_compatible_p(),
> > so at least don't screw up compilation for them and let C++ users
> > pick btf_dump__new vs btf_dump__new_deprecated explicitly.
> >
> > [0] https://github.com/libbpf/libbpf/issues/283#issuecomment-986100727
> > Fixes: 6084f5dc928f ("libbpf: Ensure btf_dump__new() and btf_dump_opts are future-proof")
> > Signed-off-by: Andrii Nakryiko <andrii@xxxxxxxxxx>
> > Signed-off-by: Jiri Olsa <jolsa@xxxxxxxxxx>
>
> Acked-by: Yonghong Song <yhs@xxxxxx>


Adjusted commit message a but and applied to bpf-next, thanks.



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux