The C backend is now parallel, V's optimized compilation speed is now 12 times faster on a 14 core cpu: 2.1s vs 24s. (M4 MacBook Pro)
Note, that the C optimizers work best when they have all the info about the program. That's why many C/C++ devs merge all project files into a single file before doing a production build. (Don't do this in V, it does it for you!đŸ™‚) So to achieve the absolutely best performance before doing a production build, run v -prod on a single thread and a single file (without -parallel-cc). v -prod -parallel-cc ... is a good compromise for achieving significantly better performance compared to the unoptimized v ..., while incurring only a minor increase in compilation time.