public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "shung-hsi.yu at suse dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109253] libbpf: failed to find BTF info for global/extern symbol '__divdi3'
Date: Thu, 30 Nov 2023 01:38:28 +0000 [thread overview]
Message-ID: <bug-109253-4-MrpfzKY0ir@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109253-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109253
--- Comment #7 from Shung-Hsi Yu <shung-hsi.yu at suse dot com> ---
(In reply to Jose E. Marchesi from comment #6)
> 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.
That's awesome! Thank you and others so much for this.
next prev parent reply other threads:[~2023-11-30 1:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 2:27 [Bug debug/109253] New: " james.hilliard1 at gmail dot com
2023-03-23 16:08 ` [Bug target/109253] " david.faust at oracle dot com
2023-08-18 13:57 ` jemarch at gcc dot gnu.org
2023-11-28 15:23 ` cvs-commit at gcc dot gnu.org
2023-11-28 15:48 ` jemarch at gcc dot gnu.org
2023-11-29 11:41 ` shung-hsi.yu at suse dot com
2023-11-29 12:45 ` jemarch at gcc dot gnu.org
2023-11-30 1:38 ` shung-hsi.yu at suse dot com [this message]
2024-01-20 17:23 ` pinskia at gcc dot gnu.org
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=bug-109253-4-MrpfzKY0ir@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).