From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3E1AD385AC2E; Wed, 29 Nov 2023 12:45:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3E1AD385AC2E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701261915; bh=OdOUQaOTDdPDkjDsDi2xOa6uGPcMVhN23E3Pxiv5dQA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=iXaPRHJuMv8Y9L4bw2ohE9ChYVFWcRjBPHeH+x9u6xQ0IuH4L6ZiyHrUaFsB8OWpb +Sxx6kVvQ6qp4x3bIGCliVsXCIbHz/UBTYOz9Cl5eA5eUFqd5AXCTfk46aLc3on0eX riJ/evAwJ3YHQstAszXbN5QR5NphZ/gyEIZnFFLo= From: "jemarch at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109253] libbpf: failed to find BTF info for global/extern symbol '__divdi3' Date: Wed, 29 Nov 2023 12:45:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jemarch at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109253 --- Comment #6 from Jose E. Marchesi --- (In reply to Shung-Hsi Yu from comment #5) > any chance we will also have this fix in GCC 13? Yes. We plan to backport this and many other BPF related fixes and improvements to GCC 10, 11, 12 and 13, once the port is capable of building= all the kernel BPF selftests. We are almost there.=