public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Ulf Samuelsson <binutils@emagii.com>
Cc: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: RFC: generating a header using the linker (ASCII, ASCIZ commands)
Date: Mon, 13 Feb 2023 13:33:39 +0100	[thread overview]
Message-ID: <ece91124-a230-dda6-b911-2656440d7898@suse.com> (raw)
In-Reply-To: <73f54df1-c236-4c4a-c161-85ebe6d6f7b7@emagii.com>

On 13.02.2023 12:12, Ulf Samuelsson via Binutils wrote:
> Den 2023-02-13 kl. 11:09, skrev Nick Clifton:
>>> One of the problems was that we wanted to generate a header,
>>> and for various reasons, it was desirable to have the linker generate 
>>> the header
>>
>> From the sound of what you have written below it would be
>> easier to use the assembler to create the header and then just
>> include it as another object file when you perform your link.
>> That together with a customised linker script should allow you
>> to achieve what you want without having to add new code to the
>> linker.
> 
> One of the problems is time of build.
> The header should contain the time when things are linked together, not 
> when things are compiled.
> 
> Another is that one of the fields is the size of the application which 
> is only known at link time.
> 
> Doing things in the linker seems to be the cleanest way.
> 
> We would probably have the header is in a separate file which is 
> included in the linker script.

Otherwise I would be wondering if you're not really defining a new binary
format (potentially an extension of an existing one), at which point it
might be best to also treat it as such in binutils / ld.

Jan

  reply	other threads:[~2023-02-13 12:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 17:36 Ulf Samuelsson
2023-02-13 10:09 ` Nick Clifton
2023-02-13 11:12   ` Ulf Samuelsson
2023-02-13 12:33     ` Jan Beulich [this message]
2023-02-13 15:54       ` Ulf Samuelsson
2023-02-13 14:11     ` Nick Clifton
2023-02-13 16:04       ` Ulf Samuelsson
2023-02-14 16:06         ` Nick Clifton
2023-02-14 18:12           ` Ulf Samuelsson
2023-02-15 20:07       ` RFC: generating a header using the linker (CRC calculation) Ulf Samuelsson
2023-02-15 21:01         ` Ulf Samuelsson
2023-02-15 21:29           ` Paul Koning
2023-02-15 22:08             ` Ulf Samuelsson
2023-02-15 22:11               ` Paul Koning
2023-02-16  6:45                 ` Ulf Samuelsson

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=ece91124-a230-dda6-b911-2656440d7898@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@emagii.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@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).