public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: libc-alpha@sourceware.org
Cc: Yonghong Song <yhs@fb.com>, Richard Henderson <rth@twiddle.net>,
	Mark Wielaard <mark@klomp.org>
Subject: [PATCH] elf.h: Add BPF relocation types.
Date: Sat, 16 Jun 2018 21:46:00 -0000	[thread overview]
Message-ID: <20180616214515.10737-1-mark@klomp.org> (raw)

The BPF ELF format has new relocation types R_BPF_64_64 and R_BPF_64_32.
The existing R_BPF_MAP_FD was an extension that never got implemented.
Remove it, because its constant conflicts with the official R_BPF_64_64.
---
 ChangeLog | 5 +++++
 elf/elf.h | 3 ++-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index 9dd87eebb8..40175d254a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2018-06-16  Mark Wielaard  <mark@klomp.org>
+
+	* elf/elf.h (R_BPF_MAP_FD): Removed.
+	(R_BPF_64_64, R_BPF_64_32): New.
+
 2018-06-15  Samuel Thibault  <samuel.thibault@ens-lyon.org>
 
 	* include/sys/sendfile.h (__sendfile64): Declare hidden prototype.
diff --git a/elf/elf.h b/elf/elf.h
index a5b2811ce0..75043bcbf9 100644
--- a/elf/elf.h
+++ b/elf/elf.h
@@ -3850,7 +3850,8 @@ enum
 /* BPF specific declarations.  */
 
 #define R_BPF_NONE		0	/* No reloc */
-#define R_BPF_MAP_FD		1	/* Map fd to pointer */
+#define R_BPF_64_64		1
+#define R_BPF_64_32		10
 
 /* Imagination Meta specific relocations. */
 
-- 
2.17.0

             reply	other threads:[~2018-06-16 21:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-16 21:46 Mark Wielaard [this message]
2018-06-19 20:06 ` Florian Weimer
2018-06-19 20:34   ` Mark Wielaard
2018-06-19 20:38     ` Yonghong Song
2018-06-21 14:53 ` Florian Weimer
2018-06-21 15:29 ` Carlos O'Donell
2018-06-21 16:48   ` Mark Wielaard

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=20180616214515.10737-1-mark@klomp.org \
    --to=mark@klomp.org \
    --cc=libc-alpha@sourceware.org \
    --cc=rth@twiddle.net \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).