Re: [PATCH bpf-next] libbpf: handle invalid typedef emitted by old GCC

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

Subject: Re: [PATCH bpf-next] libbpf: handle invalid typedef emitted by old GCC
From: Martin Lau <kafai@xxxxxx>
Date: Fri, 11 Oct 2019 16:06:43 +0000
Accept-language: en-US
Cc: "bpf@xxxxxxxxxxxxxxx" <bpf@xxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxxxxxx" <netdev@xxxxxxxxxxxxxxx>, Alexei Starovoitov <ast@xxxxxx>, "daniel@xxxxxxxxxxxxx" <daniel@xxxxxxxxxxxxx>, "john.fastabend@xxxxxxxxx" <john.fastabend@xxxxxxxxx>, "andrii.nakryiko@xxxxxxxxx" <andrii.nakryiko@xxxxxxxxx>, Kernel Team <Kernel-team@xxxxxx>
In-reply-to: <20191011032901.452042-1-andriin@fb.com>
Thread-index: AQHVf+QVzxwBEedph0qBKgb7eCyB7KdVm/MA
Thread-topic: [PATCH bpf-next] libbpf: handle invalid typedef emitted by old GCC

On Thu, Oct 10, 2019 at 08:29:01PM -0700, Andrii Nakryiko wrote:
> Old GCC versions are producing invalid typedef for __gnuc_va_list
> pointing to void. Special-case this and emit valid:
> 
> typedef __builtin_va_list __gnuc_va_list;
Acked-by: Martin KaFai Lau <kafai@xxxxxx>

References:
- [PATCH bpf-next] libbpf: handle invalid typedef emitted by old GCC
  - From: Andrii Nakryiko

Prev by Date: [PATCH] perf_event: Add support for LSM and SELinux checks
Next by Date: [PATCH bpf-next 1/3] bpf: preserve command of the process that loaded the program
Previous by thread: [PATCH bpf-next] libbpf: handle invalid typedef emitted by old GCC
Next by thread: RE: [PATCH bpf-next] libbpf: handle invalid typedef emitted by old GCC
Index(es):
- Date
- Thread

[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