Hi all,

Thanks to Johan Engelen's awesome work, the first usable LDC version with a D-based frontend is inching closer and closer.

There is still much left to be done, as it is in the aftermath of every frontend merge. But I've fixed some of the most severe bugs, and the test suite runners are up and running now again:

---
The following tests FAILED:
        242 - std.math (Failed)
        243 - std.datetime (Failed)
        253 - std.zip (Failed)
        262 - std.string (Failed)
        267 - std.uni (Failed)
        321 - std.net.curl (SEGFAULT)
        329 - std.regex.internal.tests (SEGFAULT)
        603 - std.math-debug (Failed)
        604 - std.datetime-debug (Failed)
        614 - std.zip-debug (Failed)
        623 - std.string-debug (Failed)
        682 - std.net.curl-debug (SEGFAULT)
        687 - std.regex-debug (SEGFAULT)
        690 - std.regex.internal.tests-debug (SEGFAULT)
        732 - dmd-testsuite-debug (Failed)
        734 - dmd-testsuite (Failed)
---

The current state is available from the "merge-2.069" branch on ldc-developers/ldc. For now, you might want to use DMD to build the frontend parts still, as there appears to be a C++ ABI bug affecting it in LDC still.

 — David

On Thursday, 4 February 2016 at 03:36:14 UTC, David Nadlinger wrote:
> Hi all,
>
> Thanks to Johan Engelen's awesome work, the first usable LDC version with a D-based frontend is inching closer and closer.
>
> There is still much left to be done, as it is in the aftermath of every frontend merge. But I've fixed some of the most severe bugs, and the test suite runners are up and running now again:
>
> ---
> The following tests FAILED:
>         242 - std.math (Failed)
>         243 - std.datetime (Failed)
>         253 - std.zip (Failed)
>         262 - std.string (Failed)
>         267 - std.uni (Failed)
>         321 - std.net.curl (SEGFAULT)
>         329 - std.regex.internal.tests (SEGFAULT)
>         603 - std.math-debug (Failed)
>         604 - std.datetime-debug (Failed)
>         614 - std.zip-debug (Failed)
>         623 - std.string-debug (Failed)
>         682 - std.net.curl-debug (SEGFAULT)
>         687 - std.regex-debug (SEGFAULT)
>         690 - std.regex.internal.tests-debug (SEGFAULT)
>         732 - dmd-testsuite-debug (Failed)
>         734 - dmd-testsuite (Failed)
> ---

Great news!  I was hoping the D frontend merge wouldn't take that long.  Is it normal for phobos tests to be failing on a merge, ie even when the frontend was C++?

> The current state is available from the "merge-2.069" branch on ldc-developers/ldc. For now, you might want to use DMD to build the frontend parts still, as there appears to be a C++ ABI bug affecting it in LDC still.

Hmm, I was hoping to build ldc 2.069 on ARM too, which will require using ldc to compile the D frontend to ARM.  I thought dmd upstream builds fine with ldc, is this something different from the bug that build had before?

On Thursday, 4 February 2016 at 04:47:52 UTC, Joakim wrote:
> Is it normal for phobos tests to be failing on a merge, ie even when the frontend was C++?

Quite normal, unfortunately, since the AST semantics tend to silently change from time to time.

> Hmm, I was hoping to build ldc 2.069 on ARM too, which will require using ldc to compile the D frontend to ARM.  I thought dmd upstream builds fine with ldc, is this something different from the bug that build had before?

All I can say is that it blew up quite more spectacularly with LDC at first than with DMD – it might be an OS X-only issue, though, since I didn't have time to go back to trying another LDC/LDC build yet.

 — David

On Thursday, 4 February 2016 at 03:36:14 UTC, David Nadlinger wrote:
> Thanks to Johan Engelen's awesome work
> [...]
> I've fixed some of the most severe bugs

Very nice, thx guys!

On Thursday, 4 February 2016 at 03:36:14 UTC, David Nadlinger wrote:
> I've fixed some of the most severe bugs, and the test suite runners are up and running now again:

Great!

> The current state is available from the "merge-2.069" branch on ldc-developers/ldc. For now, you might want to use DMD to build the frontend parts still, as there appears to be a C++ ABI bug affecting it in LDC still.

Sounds like something fun I can work on after I´m back from vacation :)

cheers,
  Johan

The only remaining failures are a few dmd-testsuite test cases and std.{string, uni}. I'll leave it at that for now so Johan can have some fun, too. ;)

 — David

On Sunday, 7 February 2016 at 19:58:28 UTC, David Nadlinger wrote:
> The only remaining failures are a few dmd-testsuite test cases and std.{string, uni}.

The only remaining issue is "-cov" on Linux (it works fine on OS X), so we already have a few green marks on Travis!
https://travis-ci.org/ldc-developers/ldc/builds/109185087

@kinke, Could you install DMD on AppVeyor? Thanks!
https://ci.appveyor.com/project/kinke/ldc/build/1.0.874/job/0kdaehw73stq16hp
(locally on my Windows machine, things already work with default installed DMD)

All green!

https://travis-ci.org/ldc-developers/ldc/builds/109326006

On 15 Feb 2016, at 14:02, Johan Engelen via digitalmars-d-ldc wrote:
> All green!
>
> https://travis-ci.org/ldc-developers/ldc/builds/109326006

Nice!

2.070 has only a couple more failures as well, so that should be quick to fix.

 — David

On Monday, 15 February 2016 at 13:02:41 UTC, Johan Engelen wrote:
> All green!
>
> https://travis-ci.org/ldc-developers/ldc/builds/109326006

Very nice. Win64 still needs some love though... :)