3 ms·
> vlang is really fast, recompiling itself entirely within a couple of seconds. Does V still just output C and use TCC under the hood?
by von_lohengramm 1y ago
> vlang is really fast, recompiling itself entirely within a couple of seconds.
Does V still just output C and use TCC under the hood?
- shakna 1y agoYes. [0] https://github.com/vlang/v/blob/master/Makefile#L18 https://github.com/vlang/v/blob/master/Makefile#L18
- giancarlostoro 1y agoSo in theory, I can make Nim do the same?
- cb321 1y agoI use tcc with Nim all the time and it yields almost interpreted REPL-like code-iteration speed (like 100-500ms per compile-link - almost ENTER-see-results). As a warning, you need to be sure --lineDir=off in your nim.cfg or config.nims (to side-step the infinite loop mentioned in https://github.com/nim-lang/Nim/pull/23488 https://github.com/nim-lang/Nim/pull/23488). You may also need to --tlsEmulation=on if you do threads and you may want to --passL=-lm. tcc itself is quite fast. Faster for me than a Perl5 interpreter start-up for me (with both on trivial files). E.g., on an i7-1370P: tim "tcc -run /t/true.c" "/bin/perl</n" 58.7 +- 1.3 μs (AlreadySubtracted)Overhead 437 +- 14 μs tcc -run /t/true.c 589 +- 10 μs /bin/perl</n { EDIT: /n -> /dev/null and true.c is just "int main(int ac,char*av){return 0;}". }
- summarity 1y agoAh nice, I’ve been meaning to try TCC with Nim.