Sujet : Re: Suggested method for returning a string from a C program?
De : already5chosen (at) *nospam* yahoo.com (Michael S)
Groupes : comp.lang.cDate : 25. Mar 2025, 12:29:12
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20250325132912.000031e4@yahoo.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
User-Agent : Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-w64-mingw32)
On Tue, 25 Mar 2025 08:40:34 -0000 (UTC)
Muttley@DastardlyHQ.org wrote:
On Mon, 24 Mar 2025 18:20:02 +0000
bart <bc@freeuk.com> wibbled:
Fast compilers and also whole-program compilers open up lots of new
possibilities. But clearly you're quite happy being stuck in the
stone age.
The stone age is where they used one huge source file for a program.
Separate compilation process and modularization/# of source files are
not directly related.
When the speed (or size, or correctness) is paramount, separate
compilation is inevitably inferior to whole-program compilation.
If people still use separate compilation, it does not happen because
it is good thing, but because compilers are too slow. Or, if we're
talking about Unix world, out of inertia.
In Windows world release builds of majority of C/C++ software is done
LTCG. Most developers do not even think about it, its a default. Even
in Linux world, projects that care about experience of their users,
like for example Firefox, use LTCG as a minimum, sometimes even going
for profile-guided whole program compilations.