On 9/27/16 12:48 PM, Ilya Yaroshenko wrote:
> On Tuesday, 27 September 2016 at 10:44:28 UTC, Guillaume Piolat wrote:
>> On Tuesday, 27 September 2016 at 01:17:16 UTC, Andrei Alexandrescu wrote:
>>> I'm not going to argue this much further. Essentially Mir is touted
>>> as a highly generic and portable library. Having it only work on one
>>> language implementation works against that statement, the credibility
>>> of Mir, and the credibility of D as an universal platform for
>>> creating fast code.
>>
>> Isn't it just a matter of adding "version(LDC)" around the more
>> optimized blocks?
>> Having it work in DMD, however slower, is good enough.
>
> 50 times slower for modern CPUs.

Just to reiterate my point: I'd say a 30% penalty would be still within batting range of the best out there and would be my lower bound for declaring dmd/Mir a success. -- Andrei

On 9/27/16 12:36 PM, Ilya Yaroshenko wrote:
> On Tuesday, 27 September 2016 at 10:20:09 UTC, Andrei Alexandrescu wrote:
>> On 9/27/16 10:50 AM, Ilya Yaroshenko wrote:
>>> On Tuesday, 27 September 2016 at 07:01:08 UTC, Jacob Carlborg wrote:
>>>> On 2016-09-26 21:49, bachmeier wrote:
>>>>
>>>>> [...]
>>>>
>>>> He mentions several front end issues, those apply to LDC as well.
>>>
>>> No, LDC for example does not have the issue
>>> https://issues.dlang.org/show_bug.cgi?id=16488 and others too.
>>
>> Can we make sure all issues that Mir has with dmd and gdc be present
>> in bugzilla and tagged with "Mir"? Thanks! -- Andrei
>
> Will fill them tomorrow --Ilya

Awes, thx. -- Andrei

On Tuesday, 27 September 2016 at 15:31:41 UTC, Andrei Alexandrescu wrote:
> On 9/27/16 12:36 PM, Ilya Yaroshenko wrote:
>> On Tuesday, 27 September 2016 at 10:20:09 UTC, Andrei Alexandrescu wrote:
>>> On 9/27/16 10:50 AM, Ilya Yaroshenko wrote:
>>>> On Tuesday, 27 September 2016 at 07:01:08 UTC, Jacob Carlborg wrote:
>>>>> On 2016-09-26 21:49, bachmeier wrote:
>>>>>
>>>>>> [...]
>>>>>
>>>>> He mentions several front end issues, those apply to LDC as well.
>>>>
>>>> No, LDC for example does not have the issue
>>>> https://issues.dlang.org/show_bug.cgi?id=16488 and others too.
>>>
>>> Can we make sure all issues that Mir has with dmd and gdc be present
>>> in bugzilla and tagged with "Mir"? Thanks! -- Andrei
>>
>> Will fill them tomorrow --Ilya
>
> Awes, thx. -- Andrei

DMD performance Issues list https://github.com/libmir/mir/wiki/Compiler-and-druntime-bugs#dmd-performance-issues

On Tuesday, 27 September 2016 at 10:36:09 UTC, Walter Bright wrote:
> On 9/27/2016 2:21 AM, Ilya Yaroshenko wrote:
>> Bug report for (5) https://issues.dlang.org/show_bug.cgi?id=16550 :
>
> Thank you. Please see my comment on it. Also, please tag all SIMD Bugzilla issues with the SIMD keyword (I already did it for 16550).

Done. Full DMD performance Issues related to Mir list can be found here https://github.com/libmir/mir/wiki/Compiler-and-druntime-bugs#dmd-performance-issues

Thank you,
Ilya

On 2016-09-28 11:06, Ilya Yaroshenko wrote:

> Done. Full DMD performance Issues related to Mir list can be found here
> https://github.com/libmir/mir/wiki/Compiler-and-druntime-bugs#dmd-performance-issues

It found be better to use the tag field in bugzilla instead of putting "[Mir]" in the title.

-- 
/Jacob Carlborg

On Wednesday, 28 September 2016 at 09:41:02 UTC, Jacob Carlborg wrote:
> On 2016-09-28 11:06, Ilya Yaroshenko wrote:
>
>> Done. Full DMD performance Issues related to Mir list can be found here
>> https://github.com/libmir/mir/wiki/Compiler-and-druntime-bugs#dmd-performance-issues
>
> It found be better to use the tag field in bugzilla instead of putting "[Mir]" in the title.

There are both tags and "[Mir]"

On Monday, 26 September 2016 at 22:34:59 UTC, Andrei Alexandrescu wrote:
> That would work out as long as interaction is seamless. Please advise. Overall: I think Ilya's work can make a real difference for D, and we can't afford it to not work with the reference implementation. -- Andrei

There is no point in running number crunching with a crappy optimizer.
The time to make it somehow still work, albeit slow, is much better spent on completing the science ecosystem.

On Wednesday, 28 September 2016 at 09:04:23 UTC, Ilya Yaroshenko wrote:
> On Tuesday, 27 September 2016 at 15:31:41 UTC, Andrei Alexandrescu wrote:
>> On 9/27/16 12:36 PM, Ilya Yaroshenko wrote:
>>> On Tuesday, 27 September 2016 at 10:20:09 UTC, Andrei Alexandrescu wrote:
>>>> On 9/27/16 10:50 AM, Ilya Yaroshenko wrote:
>>>>> On Tuesday, 27 September 2016 at 07:01:08 UTC, Jacob Carlborg wrote:
>>>>>> On 2016-09-26 21:49, bachmeier wrote:
>>>>>>
>>>>>>> [...]
>>>>>>
>>>>>> He mentions several front end issues, those apply to LDC as well.
>>>>>
>>>>> No, LDC for example does not have the issue
>>>>> https://issues.dlang.org/show_bug.cgi?id=16488 and others too.
>>>>
>>>> Can we make sure all issues that Mir has with dmd and gdc be present
>>>> in bugzilla and tagged with "Mir"? Thanks! -- Andrei
>>>
>>> Will fill them tomorrow --Ilya
>>
>> Awes, thx. -- Andrei
>
> DMD performance Issues list https://github.com/libmir/mir/wiki/Compiler-and-druntime-bugs#dmd-performance-issues

Maybe this one one too:

https://issues.dlang.org/show_bug.cgi?id=16497

The backend can allocate on the pointer stack for a move. It's not just about DMD being not the fatest compiler, it's about something stupid done by the code gen.

On Thursday, 29 September 2016 at 09:22:56 UTC, Martin Nowak wrote:
> On Monday, 26 September 2016 at 22:34:59 UTC, Andrei Alexandrescu wrote:
>> That would work out as long as interaction is seamless. Please advise. Overall: I think Ilya's work can make a real difference for D, and we can't afford it to not work with the reference implementation. -- Andrei
>
> There is no point in running number crunching with a crappy optimizer.

But there _is_ a point in _developing_ number crunching software with said compiler, and switch to a better one in production.

On Thursday, 29 September 2016 at 09:22:56 UTC, Martin Nowak wrote:
> On Monday, 26 September 2016 at 22:34:59 UTC, Andrei Alexandrescu wrote:
>> That would work out as long as interaction is seamless. Please advise. Overall: I think Ilya's work can make a real difference for D, and we can't afford it to not work with the reference implementation. -- Andrei

Yes agreed, we don't want this to become the reference implementation.
But just as the OP mentioned I think the cost for a workable dmd support is fairly high, in terms of missing dmd features and porting mir to dmd.

Integrating this with a pre-compiled ldc library is a fantastic idea OTOH.
If we can make this work, it will be much less effort and yield the fastest implementation. Also would speed up the development cycle a bit b/c the kernels don't need to be recompiled/optimized.