Re: dmdcache
On 4/25/20 5:30 AM, John Colvin wrote: > how does this differ from just using make? make is great and I love it (really) but it works at a coarser level. There is no way for it to know that a particular command will produce the same output. As I understand it, dmdcache is supposed to be similar to ccache, which we already use with make to speed up our C++ compilations: https://ccache.dev/ Ali
Re: dmdcache
On 27/04/2020 1:52 AM, Ali Çehreli wrote: However, currently dmdcache doesn't seem to look for string imports; opportunity for improvement. :) That should not be necessary if you base it on -J instead.
Re: dmdcache
On 4/25/20 9:01 AM, bauss wrote: > On Saturday, 25 April 2020 at 10:35:49 UTC, Stefan Koch wrote: >> The main problem with this is that it does not take string imports >> into account [...] > Yeah, doesn't look like it which means it might not be useful in > projects that does a lot of compile-time stuff. > > There is no way to determine the import statements either as those > themselves can be generated at compile-time. Luckily, dmd gives all of that information with both -v and -X command line switches. However, currently dmdcache doesn't seem to look for string imports; opportunity for improvement. :) Ali
Re: dmdcache
On 4/25/20 4:39 AM, Johan wrote: On Saturday, 25 April 2020 at 10:17:50 UTC, Ali Çehreli wrote: A colleague of mine has written dmdcache which may be very useful for some projects: https://github.com/seeraven/dmdcache It drops our build time from 8 minutes to 45 seconds Hey Ali, Did you also try with LDC's built-in object file caching (asm codegen caching) ? Cheers, Johan That sounds very promising. Time to introduce ldc to the project. Ali
