From: Steve Simon <steve@quintile.net>
To: tuhs@tuhs.org
Subject: [TUHS] Re: plan9 compiler memory use
Date: Fri, 30 Dec 2022 21:24:29 +0000 [thread overview]
Message-ID: <CD26580C-F27D-485E-844D-A71BBEE1B97B@quintile.net> (raw)
In-Reply-To: <167243231558.2485736.5509457353063331582@minnie.tuhs.org>
at the risk of making a fool of myself - there are several people far better qualified here, however…
my memory is that the plan9 linker could be easily rebuilt to use malloc and free in the traditional style, reducing its memory footprint - though making it much slower.
-Steve
parent reply other threads:[~2022-12-30 21:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <167243231558.2485736.5509457353063331582@minnie.tuhs.org>]
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=CD26580C-F27D-485E-844D-A71BBEE1B97B@quintile.net \
--to=steve@quintile.net \
--cc=tuhs@tuhs.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 NNTP newsgroup(s).