Re: Baby X is bor nagain

On 25/06/2024 14:48, Scott Lurndal wrote:

Michael S <already5chosen@yahoo.com> writes:

On Mon, 24 Jun 2024 18:10:20 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:
>

 

Well, what metric IS interesting?
>
You seem to not care whether an executable is 10KB, 10MB, or 10GB.
You really don't think there's correspondence with build-time?

>
No.  The ELF file contains a lot of stuff that never gets
loaded into memory (symbol tables, DWARF section data, etc);
writing to the object files by the compiler is an insignificant
component of the overall compile time.
>
Build time is not related in any way to the size of the
ELF.
>

>
That's why in my original post in this sub-thread, in order to give
a feeling of the size of compiler's job I gave the size of text
segment rather than size of the elf.
The size of text segment is, of course, not a good measure of
compiler's job, esp. when we are trying to compare compile jobs for
different target architectures, but it is less bad than any alternative
measure [that is not too hard to gather] that I can think of.
If you can think about anything better, please tell us.

 Does the compiled code meet functional and performance  specifications?
 That's the only criteria that matters.  Size of the executable
and compilation speed are basically irrelevent metrics in my
experience.

If apparently anything goes, and you don't care how slow a tool is or how big its output, how do you detect unnecessary bloat?
How do you detect gratuitous use of machine resources?
BTW since you and DB are both keen on products like Python, I'm curious as to how you reconcile the fast, streamlined bytecode compilers within such languages, which do no analysis and no optimising, with the heavyweight, 'professional' compilers used for translating C code.
Why is fast, TCC-like translation a terrible idea for C code and makes it a 'toy' compiler, but perfectly fine for Python code? Bear in mind that the worst TCC code will be a magnitude faster than any Python code, if it is the speed of the output that you are concerned with.
(It's lucky that the people behind gcc didn't write CPython's bytecode compiler!)