Hi all,

What is blocking the next (2.066-based) release?

The current situation regarding template/cross-module inlining is rather unfortunate, but it shouldn't be worse than in the last release. In any case, I'm trying to come up with a design for this that actually works right now.

Cheers,
David

I'd say
https://github.com/ldc-developers/ldc/issues/736
https://github.com/ldc-developers/ldc/issues/727

As they block even basic compilation of ldc on Win.

Hi Trass3r!

On Wednesday, 8 October 2014 at 19:17:51 UTC, Trass3r wrote:
> I'd say
> https://github.com/ldc-developers/ldc/issues/736
> https://github.com/ldc-developers/ldc/issues/727
>
> As they block even basic compilation of ldc on Win.

If the issues resolved would it then make sense to create an official release for Win64? I currently don't know how many unit tests fail on Win64...

Regards,
Kai

Hi David!

On Wednesday, 8 October 2014 at 18:21:27 UTC, David Nadlinger wrote:
> What is blocking the next (2.066-based) release?

I work on implementing std.math.IeeeControl and std.math.FloatingPointControl for some non-x86 platforms. I hope to finish this by the weekend. I like to incorporate this in the next release.

Regards,
Kai

> If the issues resolved would it then make sense to create an official release for Win64? I currently don't know how many unit tests fail on Win64...

Hi Kai,
that's masked by EH:
https://github.com/ldc-developers/ldc/issues/166#issuecomment-54522891
Some druntime and all phobos tests just crash.

Then there's still the question of portable installation:
https://github.com/ldc-developers/ldc/pull/723#issuecomment-57624085

And I forgot a small backport fix:
https://github.com/ldc-developers/ldc/issues/728

Any chance of fixing EH?
It shouldn't be much effort but I don't know what could be wrong resp. how you can "debug" the unwind data and procedure.

On Wednesday, 8 October 2014 at 19:17:51 UTC, Trass3r wrote:
> https://github.com/ldc-developers/ldc/issues/736

This seems to affect LLVM 3.6 only. As such, I don't think it is relevant for the LDC release process. If you are fine with building LLVM from SVN, you won't have any issues with using LDC from Git either. Plus, you need to expect to run into problems with LLVM API changes all the time anyway. See e.g. the current status of LLVM 3.6 on Travis https://travis-ci.org/ldc-developers/ldc/jobs/37679457.

> https://github.com/ldc-developers/ldc/issues/727

Waiting for a pull request. ;)

> As they block even basic compilation of ldc on Win.

Win64/MSVC.

David

> This seems to affect LLVM 3.6 only.

Well you need the very latest version to get the EH fixes but yeah ;)

On Saturday, 11 October 2014 at 11:18:45 UTC, Trass3r wrote:
> Any chance of fixing EH?
> It shouldn't be much effort but I don't know what could be wrong resp. how you can "debug" the unwind data and procedure.

+1
I have no experience in this field, so I won't be able to help out here. But as soon as this crucial point (EH) is reasonably working, we'll be able to work on the remaining MSVCRT x64 issues and hopefully promote that platform to a first D/LDC citizen. Can't wait to see that happen. :)

On Saturday, 11 October 2014 at 13:13:52 UTC, David Nadlinger wrote:
> On Wednesday, 8 October 2014 at 19:17:51 UTC, Trass3r wrote:
>> https://github.com/ldc-developers/ldc/issues/736
>> https://github.com/ldc-developers/ldc/issues/727

Both are fixed now. Have fun. :-)

Regards,
Kai