[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165403741330.9645.14080630675434689339.git-patchwork-notify@kernel.org>
Date: Tue, 31 May 2022 22:50:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Douglas RAILLARD <douglas.raillard@....com>
Cc: bpf@...r.kernel.org, beata.michalska@....com, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, kafai@...com,
songliubraving@...com, yhs@...com, john.fastabend@...il.com,
kpsingh@...nel.org, nathan@...nel.org, ndesaulniers@...gle.com,
trix@...hat.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH v3] libbpf: Fix determine_ptr_size() guessing
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Tue, 24 May 2022 10:44:47 +0100 you wrote:
> From: Douglas Raillard <douglas.raillard@....com>
>
> One strategy employed by libbpf to guess the pointer size is by finding
> the size of "unsigned long" type. This is achieved by looking for a type
> of with the expected name and checking its size.
>
> Unfortunately, the C syntax is friendlier to humans than to computers
> as there is some variety in how such a type can be named. Specifically,
> gcc and clang do not use the same names for integer types in debug info:
>
> [...]
Here is the summary with links:
- [v3] libbpf: Fix determine_ptr_size() guessing
https://git.kernel.org/bpf/bpf-next/c/8a140f1b12f7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists