On 14 August 2015 at 11:04, Kenji Hara via dmd-internals < dmd-internals@puremagic.com> wrote:

> I have a question for the future development with ddmd.
>
> 2.067 contains some known serious codegen bugs. For example, issue 14815 ( https://issues.dlang.org/show_bug.cgi?id=14815) is not fixed in both 2.067 and 2.068. It's fixed only in git-head (would be released by 2.069?)
>
> If we will continue to use 2.067 to build new ddmd compiler, we have to avoid issue 14815 in dmd source code _forever_? There's no migration path to update host dmd compiler?
>
> - Kenji
>

I would raise PRs for regressions and maintenance bug-fixes to the 2.068 branch too.  It will take time, but 2.067 will be dropped once gdc and ldc get up to 2.068.

I know I am, and it looks like David is too still finding issues with 2.067 that will need to be upstreamed somehow...

Regards
Iain.

On Friday, 14 August 2015 at 09:18:45 UTC, Iain Buclaw wrote:
> I would raise PRs for regressions and maintenance bug-fixes to the 2.068 branch too.  It will take time, but 2.067 will be dropped once gdc and ldc get up to 2.068.
>
> I know I am, and it looks like David is too still finding issues with 2.067 that will need to be upstreamed somehow...

It means the version 2.067 of gdc and ldc contains more bug fixes than dmd 2.067. Of course it's not bad, but the bottom line is still dmd 2.067 behavior.

While we use "2.067" for the host compiler, inside dmd source code, we should avoid all codegen bugs that "dmd 2.067" has.

- Kenji
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals