Sujet : Re: xxd -i vs DIY Was: C23 thoughts and opinions
De : Bonita.Montero (at) *nospam* gmail.com (Bonita Montero)
Groupes : comp.lang.cDate : 04. Jun 2024, 09:34:16
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v3mji8$bplr$1@raubtier-asyl.eternal-september.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
User-Agent : Mozilla Thunderbird
Am 04.06.2024 um 10:01 schrieb Michael S:
On Tue, 4 Jun 2024 02:07:59 -0000 (UTC)
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
On Mon, 3 Jun 2024 18:39:55 +0200, Bonita Montero wrote:
>
MSVC quitted compilation after allocating 50GB of
memory, gcc and clang compiled for minutes.
>
Next time, don’t even bother with MSVC.
For smaller file (but still much bigger than what is likely to be
encountered in practice, 155 MB binary, 641 MB after conversion to
text) MSVC was both ~1.5x faster than gcc and had lower peak memory
consumption.
And that was a "new", slow MSVC. "Old", faster MSVC should fare even
better, if I ever dare to install it on computer with enough RAM.
I think the step through the char-array into the machinecode isn't
smart. For me it would be much smarter if there would be a tool that
compiles any binary file to an .obj file and additionaly produces sth
like that: "extern const char arr[xxx]"; this is necessary because the
xxx size should be according to the actual file size.
And there should be some options to declare if the array is preloaded
when the application starts or if it is dynammically mapped in to the
address space when touching the pages. Is there any tool like that for
Windows or Linux ?