public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jemarch at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107848] libbpf: ELF relo #0 in section #7 has unexpected type 12
Date: Wed, 22 Mar 2023 16:58:34 +0000 [thread overview]
Message-ID: <bug-107848-4-0vWvwZvLQw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107848-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107848
Jose E. Marchesi <jemarch at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Jose E. Marchesi <jemarch at gcc dot gnu.org> ---
This was due to a binutils bug. Fixed by the following binutils upstream
commits:
commit 5f784ec9277e9303eee3ce366c40ce9fa3203f3e
Author: Cupertino Miranda <cupertino.miranda@oracle.com>
Date: Fri Mar 17 15:29:36 2023 +0000
Changed ld and gas BPF tests
Recent BPF patch removed and renamed the list of relocations based on
the limitations of BPF instruction set.
This patch is a correction to the tests.
commit 551fde0ae1691a74e1fdfb2bd33e8453106c0c87
Author: Cupertino Miranda <cupertino.miranda@oracle.com>
Date: Fri Mar 17 15:27:02 2023 +0000
Reloc howto access broken for BPF
Forgot to change the logic to access the reloc howto from
bpf_elf_relocate_section.
Problem was introduced in previous BPF commit.
commit 5e4c7a839d1c0d68a4a518cf2dc8e87925575e58
Author: Cupertino Miranda <cupertino.miranda@oracle.com>
Date: Thu Mar 16 08:39:52 2023 +0000
BPF relocations review / refactoring
- Removed not needed relocations.
- Renamed relocations to match llvm and linux kernel.
Relocation changes:
R_BPF_INSN_64 => R_BPF_64_64
R_BPF_INSN_DISP32 => R_BPF_64_32
R_BPF_DATA_32 => R_BPF_64_ABS32
R_BPF_DATA_64 => R_BPF_64_ABS64
next prev parent reply other threads:[~2023-03-22 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 18:44 [Bug target/107848] New: " james.hilliard1 at gmail dot com
2022-11-23 18:46 ` [Bug target/107848] " james.hilliard1 at gmail dot com
2022-11-23 18:54 ` jose.marchesi at oracle dot com
2023-03-22 16:58 ` jemarch at gcc dot gnu.org [this message]
2023-03-22 16:59 ` 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-107848-4-0vWvwZvLQw@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).