From: "Ludovic Courtès" <ludo@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Andy Wingo <wingo@pobox.com>, <guile-devel@gnu.org>
Subject: Re: Reducing memory usage of the linker and assembler
Date: Tue, 17 Jan 2023 17:54:27 +0100 [thread overview]
Message-ID: <87sfg9cda4.fsf@gnu.org> (raw)
In-Reply-To: <87v8lgrno5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 09 Jan 2023 11:46:02 +0100")
Hello,
Ludovic Courtès <ludo@gnu.org> skribis:
> The branch replaces the ‘bv’ field of <linker-object> with ‘size’ and
> ‘writer’, the latter being a procedure that takes a bytevector and
> writes to it.
>
> At this point, ‘link-elf’ still allocates one bytevector for each linker
> object. Eventually we could rewrite those “writer” procedures to use
> binary I/O primitives instead of expecting a bytevector to write to, and
> that way we wouldn’t need those temporary bytevectors. It’s a bit
> tedious to do though.
I’ve now merged this branch into ‘main’:
3cd64feb2 * linker: Do not store entire ELF in memory when writing to a file.
4ab71e1f0 * linker: Linker object writer takes a single argument.
041f11b35 * linker, assembler: Avoid intermediate bytevectors.
d0d974360 * linker: Separate effectful part of 'add-elf-objects'.
d439a3f67 * assembler: Separate effectful part of 'link-docstrs'.
13e2d5b66 * assembler: Separate effectful part of 'link-frame-maps'.
dc0c4ccb1 * assembler: Separate effectful part of 'link-procprops'.
c7f1522c6 * assembler: Separate effectful part of 'link-dynamic-section'.
fc5eae5d0 * assembler: Separate effectful part of 'link-symtab'.
15c4c4ceb * assembler: Separate 'process-relocs' from 'patch-relocs!'.
As discussed on IRC, I’d like to tag and upload 3.0.9rc1 hopefully
tomorrow to get some testing (in particular portability testing) and
release roughly a week later.
Thoughts?
Ludo’.
prev parent reply other threads:[~2023-01-17 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 10:46 Reducing memory usage of the linker and assembler Ludovic Courtès
2023-01-17 16:54 ` Ludovic Courtès [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfg9cda4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).