From: patchwork-bot+netdevbpf@kernel.org
To: Douglas RAILLARD <douglas.raillard@arm.com>
Cc: bpf@vger.kernel.org, beata.michalska@arm.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, nathan@kernel.org, ndesaulniers@google.com,
trix@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v3] libbpf: Fix determine_ptr_size() guessing
Date: Tue, 31 May 2022 22:50:13 +0000 [thread overview]
Message-ID: <165403741330.9645.14080630675434689339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220524094447.332186-1-douglas.raillard@arm.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 24 May 2022 10:44:47 +0100 you wrote:
> From: Douglas Raillard <douglas.raillard@arm.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
prev parent reply other threads:[~2022-05-31 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 9:44 [PATCH v3] libbpf: Fix determine_ptr_size() guessing Douglas RAILLARD
2022-05-31 22:50 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165403741330.9645.14080630675434689339.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=beata.michalska@arm.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=douglas.raillard@arm.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=trix@redhat.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).