On Sunday, 3 August 2014 at 11:37:26 UTC, John Colvin wrote:
hmm i would say io ist a huge factor but this is just a guess I
have to do profiling probably i am wrong
On Sunday, 3 August 2014 at 11:19:01 UTC, Stefan Koch wrote:
On Saturday, 2 August 2014 at 22:48:35 UTC, Shammah Chancellor
On 2014-08-01 05:00:53 +0000, deadalnix said:
On Tuesday, 29 July 2014 at 13:36:39 UTC, Stefan Koch wrote:
I am happy to announce that my 32bit version of sdc
compiles the whole testsuite including mixins.
the only there are only 6 tests still failing
2 of them are dependent on size_t.siezof beeing 8.
The otherer 4 have to do with execptoion handling.
please check out the 32-branches
I haven't yet updated the submodules so you have to fetch
the 32-branch manually.
and remember that this is experimental!
please file issues on in my repo if your errors appear with
both -m64 and -m32.
if there are any questions please ask them.
A bit late, but that is awesome. I need to go through all of
this and am in holidays right now. #1 on the todo list when
i come back.
Also, it looks by using your fiber based scheduler that you
can naturally parallize compiling. Have you investigated
that at all?
I have planned to add async IO through vibe.d. that alone just
grant huge speedups. I also want to integrate SQLite or redis
based incremental compilation. I don`t think we can beat dmd
soon. But I think we can come much closer :D
Any idea what the significant bottlenecks are / what dmd is
much faster at?