vc

b.com/vlang/tccbin ./thirdparty/tcc make[2]: Entering directory '/tmp/v' make[2]: Leaving directory '/tmp/v' make[1]: Leaving directory '/tmp/v' cd ./thirdparty/tcc && git clean -xf && git pull --quiet cc -std=gnu99 -w -o v1.exe ./vc/v.c -lm -lpthread ./v1.exe -no-parallel -o v2.exe -prod cmd/v ./v2.exe -o ./v -prod cmd/v rm -rf v1.exe v2.exe Note: building an optimized binary takes much longer. It shouldn't be used with `v run`. Use `v run` without optimization, or build an optimized binary with -prod first, then run it separately. Note: `tcc` was not used, so unless you install it yourself, your backend C compiler will be `cc`, which is usually either `clang`, `gcc` or `msvc`. These C compilers, are several times slower at compiling C source code, compared to `tcc`. They do produce more optimised executables, but that is done at the cost of compilation speed. V has been successfully built V 0.2.4 0e4198f $ cat > t.sh && chmod a+x t.sh && ./t.sh > 1m_helloworld.v #!/bin/bash echo 'fn main() {' for i in {3..1000000} do echo ' println("hello world")' done echo '}' $ time ./v 1m_helloworld.v parsed 100000 statements so far from fn main.main ... parsed 200000 statements so far from fn main.main ... parsed 300000 statements so far from fn main.main ... parsed 400000 statements so far from fn main.main ... parsed 500000 statements so far from fn main.main ... parsed 600000 statements so far from fn main.main ... parsed 700000 statements so far from fn main.main ... parsed 800000 statements so far from fn main.main ... parsed 900000 statements so far from fn main.main ... real 0m14.929s user 0m6.516s sys 0m8.031s I have also verified that TCC was indeed in use: $ mv thirdparty/tcc/tcc.exe thirdparty/tcc/tcc.exe.orig $ time ./v 1m_helloworld.v parsed 100000 statements so far from fn main.main ... parsed 200000 statements so far from fn main.main ... parsed 300000 statements so far from fn main.main ... parsed 400000 statements so far from fn main.main ... parsed 500000 statements so far from fn main.main ... parsed 600000 statements so far from fn main.main ... parsed 700000 statements so far from fn main.main ... parsed 800000 statements so far from fn main.main ... parsed 900000 statements so far from fn main.main ... ================== cc: internal compiler error: Killed (program cc1) Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions. ... ================== (Use `v -cg` to print the entire error message) builder error: ================== C error. This should never happen. This is a compiler bug, please report it using `v bug file.v`. https://github.com/vlang/v/issues/new/choose You can also use #help on Discord: https://discord.gg/vlang real 6m50.090s user 6m8.375s sys 0m31.094s (I gave up when the gcc memory usage ballooned up to 20 GB.) > What's your hardware? CPU/SSD. i7-7700 3.60 GHz, 48 GB of RAM, SSD in use, Windows 10 WSL (that's probably why kernel time is higher than average, otherwise my userland time agrees with the OP).