From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 236E5C43219 for ; Tue, 31 May 2022 22:50:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348593AbiEaWuU (ORCPT ); Tue, 31 May 2022 18:50:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33946 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348633AbiEaWuR (ORCPT ); Tue, 31 May 2022 18:50:17 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 31BB2A0062; Tue, 31 May 2022 15:50:16 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id C125FB81744; Tue, 31 May 2022 22:50:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 676F3C3411F; Tue, 31 May 2022 22:50:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1654037413; bh=1ffP4TkVvgi6sPn0mAOKdWQJeMzHw+Y5jSkgORcq0E4=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=FQGC0vPJHF2v812MbjsSI7JBhC+nkrsu62q1PtPwswLKAXkeCQEWYtmdJQvFoQlgR xR8M+hUEhlUStAGR26lDRluxMU5FZCrE6uyak8qQ3Xmarg0aQ1ajvHEDDSgLYsNPCX Jkws8dJocrLartPwQQQiRRbf/PmLPfKwPm01/EpgaBS7u5tJCWKacrGazjswn6l6pa EvCktRAykqz4V74M7LiS0bAbWItLZDrSaubQVxdP6nW91nCihi+VE7qmugEL2yFBAp A9wFT2mqi61r4B42BzxHM78OPlNYXescDTc8gxt7p1gYY5R/2RFYA6UlPwsEuOkb9q YuQQ6oSwIJo8w== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id 4B243F0394F; Tue, 31 May 2022 22:50:13 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH v3] libbpf: Fix determine_ptr_size() guessing From: patchwork-bot+netdevbpf@kernel.org Message-Id: <165403741330.9645.14080630675434689339.git-patchwork-notify@kernel.org> Date: Tue, 31 May 2022 22:50:13 +0000 References: <20220524094447.332186-1-douglas.raillard@arm.com> In-Reply-To: <20220524094447.332186-1-douglas.raillard@arm.com> To: Douglas RAILLARD 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 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hello: This patch was applied to bpf/bpf-next.git (master) by Andrii Nakryiko : On Tue, 24 May 2022 10:44:47 +0100 you wrote: > From: Douglas Raillard > > 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