On Fri, 01 Aug 2014 23:16:43 +0000
Stefan Koch via Digitalmars-d-announce
<digitalmars-d-announce@puremagic.com> wrote:

> Thanks for your cooperation!
you're welcome. %-)

On Friday, 1 August 2014 at 09:02:23 UTC, ketmar via Digitalmars-d-announce wrote:
> On Wed, 30 Jul 2014 09:39:15 +0000
> Stefan Koch via Digitalmars-d-announce
> <digitalmars-d-announce@puremagic.com> wrote:
>
> can't link it. GNU/Linux, x86, latest DMD from git.
>
> lib/libd.a(semantic.o): In function
> `_D1d3ast10expression56__T15UnaryExpressionTC1d3ast10expression13AstExpressionZ15UnaryExpression11__T6__ctorZ6__ctorMFS1d8location8LocationE1d3ast10expression7UnaryOpC1d3ast10expression13AstExpressionZC1d3ast10expression56__T15UnaryExpressionTC1d3ast10expression13AstExpressionZ15UnaryExpression': ...
> and so on
>
> LLVM 3.4.2, so prerequisites are ok.

I got that error recently. It is an LLVM bug and upgrading LLVM should do the trick.

On Sat, 02 Aug 2014 03:27:58 +0000
deadalnix via Digitalmars-d-announce
<digitalmars-d-announce@puremagic.com> wrote:

> I got that error recently. It is an LLVM bug and upgrading LLVM should do the trick.
in my case it was nothing with LLVM. sdc-32 needs dmd-2.065, and i'm using dmd-2.066-master. switching to 2.065 resolves the issue.

On 2014-08-01 05:00:53 +0000, deadalnix said:

> On Tuesday, 29 July 2014 at 13:36:39 UTC, Stefan Koch wrote:
>> Hello,
>> 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
>> on https://github.com/UplinkCoder/sdc
>> and https://github.com/UplinkCoder/libd-llvm
>> and https://github.com/UplinkCoder/libd
>> 
>> 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.

The methodology of SDC is awesome deadalnix.   I'm very happy this is moving forward.  It reduces the code to implement a D compiler by a substantial amount.  When I have more time I plan to start contributing.

On 2014-08-01 05:00:53 +0000, deadalnix said:

> On Tuesday, 29 July 2014 at 13:36:39 UTC, Stefan Koch wrote:
>> Hello,
>> 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
>> on https://github.com/UplinkCoder/sdc
>> and https://github.com/UplinkCoder/libd-llvm
>> and https://github.com/UplinkCoder/libd
>> 
>> 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?

On Saturday, 2 August 2014 at 22:48:35 UTC, Shammah Chancellor wrote:
> On 2014-08-01 05:00:53 +0000, deadalnix said:
>
>> On Tuesday, 29 July 2014 at 13:36:39 UTC, Stefan Koch wrote:
>>> Hello,
>>> 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
>>> on https://github.com/UplinkCoder/sdc
>>> and https://github.com/UplinkCoder/libd-llvm
>>> and https://github.com/UplinkCoder/libd
>>> 
>>> 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

On Fri, 01 Aug 2014 15:49:09 +0000
Stefan Koch via Digitalmars-d-announce
<digitalmars-d-announce@puremagic.com> wrote:

> it must have a commit I have squashed.
> I do this quite often since sometimes I commit stuff that causes
> my build to fail :p
btw, please, don't do that. just revert commits, there's no need to rewrite the history hard way. or use branches and do cherry-picking, it's easy once you get used to it.

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 wrote:
>> On 2014-08-01 05:00:53 +0000, deadalnix said:
>>
>>> On Tuesday, 29 July 2014 at 13:36:39 UTC, Stefan Koch wrote:
>>>> Hello,
>>>> 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
>>>> on https://github.com/UplinkCoder/sdc
>>>> and https://github.com/UplinkCoder/libd-llvm
>>>> and https://github.com/UplinkCoder/libd
>>>> 
>>>> 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?

On Sunday, 3 August 2014 at 11:37:26 UTC, John Colvin wrote:
> 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 wrote:
>>> On 2014-08-01 05:00:53 +0000, deadalnix said:
>>>
>>>> On Tuesday, 29 July 2014 at 13:36:39 UTC, Stefan Koch wrote:
>>>>> Hello,
>>>>> 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
>>>>> on https://github.com/UplinkCoder/sdc
>>>>> and https://github.com/UplinkCoder/libd-llvm
>>>>> and https://github.com/UplinkCoder/libd
>>>>> 
>>>>> 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?
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:31:10 UTC, ketmar via Digitalmars-d-announce wrote:
> On Fri, 01 Aug 2014 15:49:09 +0000
> Stefan Koch via Digitalmars-d-announce
> <digitalmars-d-announce@puremagic.com> wrote:
>
>> it must have a commit I have squashed.
>> I do this quite often since sometimes I commit stuff that causes my build to fail :p
> btw, please, don't do that. just revert commits, there's no need to
> rewrite the history hard way. or use branches and do cherry-picking,
> it's easy once you get used to it.

yeah I will try to keep it clean :D