Required DMD changes for Mir and few thoughts about D future

[Robert Rat via Digitalmars-d]

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.