public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Fangrui Song via Libc-alpha <libc-alpha@sourceware.org>
Cc: Fangrui Song <maskray@google.com>,  binutils@sourceware.org
Subject: Re: [PATCH] elf: Support DT_RELR relative relocation format [BZ #27924]
Date: Fri, 08 Oct 2021 17:39:32 +0200	[thread overview]
Message-ID: <87zgrjy18r.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20211008065740.1485737-1-maskray@google.com> (Fangrui Song via Libc-alpha's message of "Thu, 7 Oct 2021 23:57:40 -0700")

* Fangrui Song via Libc-alpha:

> @@ -887,7 +893,10 @@ typedef struct
>  #define DT_PREINIT_ARRAY 32		/* Array with addresses of preinit fct*/
>  #define DT_PREINIT_ARRAYSZ 33		/* size in bytes of DT_PREINIT_ARRAY */
>  #define DT_SYMTAB_SHNDX	34		/* Address of SYMTAB_SHNDX section */
> -#define	DT_NUM		35		/* Number used */
> +#define DT_RELRSZ	35
> +#define DT_RELR		36
> +#define DT_RELRENT	37
> +#define	DT_NUM		38		/* Number used */
>  #define DT_LOOS		0x6000000d	/* Start of OS-specific */
>  #define DT_HIOS		0x6ffff000	/* End of OS-specific */
>  #define DT_LOPROC	0x70000000	/* Start of processor-specific */

<http://www.sco.com/developers/gabi/latest/ch5.dynamic.html#tag_encodings>
(Figure 5-10: Dynamic Array Tags, d_tag) still ends at 34, and I'm
worried about collisions with these numbers.

Do you know what the official allocation status for the new constants
is?

  reply	other threads:[~2021-10-08 15:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08  6:57 Fangrui Song
2021-10-08 15:39 ` Florian Weimer [this message]
2021-10-08 16:36   ` Fangrui Song
2021-10-08 19:41     ` Cary Coutant
2021-10-08 16:51 ` H.J. Lu
2021-10-08 17:37   ` Fangrui Song
2021-10-08 17:43     ` H.J. Lu
2021-10-08 18:46       ` Fangrui Song
2021-10-11  7:48 ` Jan Beulich
2021-10-11 18:43   ` Fāng-ruì Sòng
2021-10-11 22:08     ` Joseph Myers
2021-10-12  8:14       ` Jan Beulich
2021-10-12  8:18     ` Jan Beulich
2021-10-12 14:09       ` H.J. Lu
2021-10-12 16:07         ` Fāng-ruì Sòng
2021-10-13  6:00           ` Jan Beulich
2021-10-13  6:13             ` Fāng-ruì Sòng
2021-10-13  6:18               ` Fāng-ruì Sòng
2021-10-18  7:59                 ` Jan Beulich
2021-10-16 20:22   ` Fangrui Song
2021-10-26 23:28   ` Cary Coutant
2021-10-11 21:47 ` Joseph Myers

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=87zgrjy18r.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=binutils@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=maskray@google.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).