Thank you for taking the time to reply.

Stefan_Salewski >And that takes only a few seconds. That update procedure is a 
bit hidden in the documentation, but I assume devs know it. Thank you for 
letting us know. I had imagined that the difference in link times would be more 
pronounced with differential builds, but apparently I need to verify with a 
little more precision. Thank you for immediately pointing out the 
less-than-realistic nature of my benchmark.

ElegantBeef >Most times the compiler is compiled is in debug mode with a cache 
which means at most it takes ~20s. I did try mold on multiple projects with my 
5600x and I have not noticed any substantial differences in compile time Thank 
you for trying it in different environments.. I will only send a PR if I see a 
concrete and clear difference after more verification. Thank you all for your 
valuable time.

What's a little peculiar in my environment is that I have a RAM disk in it, but 
I'm wondering if the RAM disk has any effect since nimcache uses the same 
directory in the full build of the Nim compiler itself, but it doesn't seem to 
make a clear difference in different environments.

In any case, you are right that Nim compiles very fast even with gcc ld or 
clang lld, so there is not much point in actively changing it.

When I can verify it more correctly and with more patterns, or when the 
situation changes, we may suggest it again.

Reply via email to