← Back to context

Comment by ylluminate

3 years ago

He is in fact reading it, please look again at what he pasted. It really seems somehow you're getting your wires crossed.

5 comments

ylluminate

Reply
lifthrasiir  3 years ago

No he didn't understand at all. Both the OP and I'm saying that while `make` claims that tcc was not used, the compiler does seem to use tcc even in that case. I have demonstrated that this is a plausible explanation by moving the tcc binary and showing the stark performance difference.

(This is my final response on this matter. I have already given enough information and an inability to interpret it is not my business.)

  • amedvednikov  3 years ago

    I admit I misread, and you do indeed use TCC.

    I've just tested it, and turns out all C compilers are terrible at hundreds of thousands of print calls (for me Clang was stuck for minutes with 100% cpu usage).

    The claim was made about actual code, like the V compiler itself, which is about 220k loc and compiles in 0.3 seconds, not some unrealistic test with a million of prints.

    I'll make it clear on the home page with a link to the benchmark.