From: The Cuthour <cuthour@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: Introducing ELF2.0
Date: Thu, 30 Jan 2025 03:26:10 +0900 [thread overview]
Message-ID: <c8d2acad-5ea7-49ae-9a5f-f7b2f142ba58@gmail.com> (raw)
In-Reply-To: <20250129174442.GA28899@redhat.com>
Hi
>>> Some. Each port would have to enable it individually. See the #ifdef
>>> OBJC_COMPLEX_RELC configuration in gas/symbols.c.
>>
>> If the people on this list, who are struggling with 'complex
>> relocation,' have an idea of what they would like ELF to become,
>> I will respect that. In fact, Iwould encourage them to pursue it.
>
> The above functionality is compatible with - embedded in - normal ELF.
> How individual target architectures express relocations etc. is within
> their discretion, again normal ELF. If you think you have a
> significant problem that such link-time computations are needed to
> express, please share them.
The goal here is Relinkability. Even in object-oriented languages,
binary Relinkability should be a given. To achieve this, I propose
implementing at least basic arithmetic operations during the linking
phase with ELF2.0. If this proves successful, I envision further
developments leading to ELF3.0 or even 4.0 and beyond.
next prev parent reply other threads:[~2025-01-29 18:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 18:26 The Cuthour
2025-01-27 20:16 ` Frank Ch. Eigler
2025-01-27 20:22 ` Frank Ch. Eigler
2025-01-28 4:56 ` The Cuthour
[not found] ` <90e29225-b1a4-4df0-9106-898130e9da82@gmail.com>
2025-01-29 3:05 ` Frank Ch. Eigler
2025-01-29 16:25 ` The Cuthour
2025-01-29 17:44 ` Frank Ch. Eigler
2025-01-29 18:26 ` The Cuthour [this message]
2025-01-29 18:52 ` Frank Ch. Eigler
2025-01-29 19:21 ` The Cuthour
2025-01-29 19:49 ` Frank Ch. Eigler
2025-01-29 22:26 ` The Cuthour
2025-01-29 22:54 ` Frank Ch. Eigler
2025-01-29 23:25 ` The Cuthour
2025-01-30 5:55 ` The Cuthour
2025-01-30 14:28 ` The Cuthour
2025-01-30 14:55 ` Nick Alcock
2025-01-30 15:45 ` The Cuthour
2025-01-28 0:25 ` Oleg Endo
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=c8d2acad-5ea7-49ae-9a5f-f7b2f142ba58@gmail.com \
--to=cuthour@gmail.com \
--cc=binutils@sourceware.org \
--cc=fche@redhat.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).