From: Ulf Samuelsson <binutils@emagii.com>
To: binutils@sourceware.org
Subject: Re: <empty header to my ASCIZ patchset>
Date: Fri, 10 Feb 2023 18:55:25 +0100 [thread overview]
Message-ID: <ee68e779-813b-cece-ba44-6dd34fc3e7ef@emagii.com> (raw)
In-Reply-To: <20230210174404.3763-1-binutils@emagii.com>
Don't know why I did not get a subject line in my "git send-email".
Sorry about that.
A comment on the implementation.
The string is implemented internally as a number of "BYTE <value>"
statements.
This seemed to be the simplest way of doing it.
Most use of this feature will typically only have a couple of such
statements
and since this is my first addition to the code, I do not have a good
overview
of the internals.
Best Regards,
Ulf Samuelsson
Den 2023-02-10 kl. 18:44, skrev Ulf Samuelsson via Binutils:
> From binutils@emagii.com # This line is ignored.
> From: binutils@emagii.com
> Reply-To:
> Subject: ASCIZ Command for output section
> In-Reply-To:
>
> Introduce an ASCIZ command for an output section
> When generating a header for an embedded system
> there is often a need to add text information.
>
> There are arguments for generating the header in the linker
> instead of compiling the header as part of the program.
> The lack of support for strings makes this process a bit unwieldy.
>
> The ASCIZ command allows you to specify a zero-terminated string as a parameter.
>
> Example:
>
> ASCIZ "This is a string"
>
> The string contains 16 characters, but a NUL character is added to the end,
> so the areas reserved is 16+1 = 17 characters.
>
> Ideally, there should be a command which reserves a fixed size area.
>
> I:E:
>
> ASCII 20, "This is a string"
>
> but I have failed to get make this work in 'ld',
> so this patch series is limited to ASCIZ.
>
> Best Regards
> Ulf Samuelsson
>
> [PATCH 1/4] ldlex.l: Add ASCIZ token
> [PATCH 2/4] ldgram.y: Add 'ASCIZ <string>' command
> [PATCH 3/4] Parse ASCIZ command
> [PATCH 4/4] Document the ASCIZ command
>
prev parent reply other threads:[~2023-02-10 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 17:44 binutils
2023-02-10 17:44 ` [PATCH 1/4] ldlex.l: Add ASCIZ token binutils
2023-02-10 17:44 ` [PATCH 2/4] ldgram.y: Add 'ASCIZ <string>' command binutils
2023-02-10 17:44 ` [PATCH 3/4] Parse ASCIZ command binutils
2023-02-10 17:44 ` [PATCH 4/4] Document the " binutils
2023-02-10 17:55 ` Ulf Samuelsson [this message]
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=ee68e779-813b-cece-ba44-6dd34fc3e7ef@emagii.com \
--to=binutils@emagii.com \
--cc=binutils@sourceware.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).