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

On Thu, Dec 23, 2021 at 8:13 AM Yonghong Song [off-list ref] wrote:

On 12/23/21 5:17 AM, Jiri Olsa wrote:

quoted

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@kernel.org>
Signed-off-by: Jiri Olsa <jolsa@kernel.org>

Acked-by: Yonghong Song <redacted>

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