www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.ldc - Next release?

reply "David Nadlinger" <code klickverbot.at> writes:
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
Oct 08 2014
next sibling parent reply "Trass3r" <un known.com> writes:
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.
Oct 08 2014
next sibling parent reply "Kai Nacke" <kai redstar.de> writes:
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
Oct 08 2014
next sibling parent "Trass3r" <un known.com> writes:
 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
Oct 09 2014
prev sibling parent reply "Trass3r" <un known.com> writes:
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.
Oct 11 2014
parent reply "kink" <noone nowhere.com> writes:
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. :)
Oct 11 2014
parent reply "Kai Nacke" <kai redstar.de> writes:
Hi kink!

On Saturday, 11 October 2014 at 21:21:08 UTC, kink wrote:
 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. :)
Exception chaining is not implemented on Win64/MSVC. Otherwise it should work(TM). Regards, Kai
Oct 12 2014
next sibling parent reply "David Nadlinger" <code klickverbot.at> writes:
On Sunday, 12 October 2014 at 16:55:46 UTC, Kai Nacke wrote:
 Exception chaining is not implemented on Win64/MSVC. Otherwise 
 it should work(TM).
I was under the impression that both Trass3r and kink were getting random (?) EH-related crashes. I couldn't find any related issues on GitHub, though. David
Oct 12 2014
parent reply "Kai Nacke" <kai redstar.de> writes:
On Sunday, 12 October 2014 at 17:11:31 UTC, David Nadlinger wrote:
 On Sunday, 12 October 2014 at 16:55:46 UTC, Kai Nacke wrote:
 Exception chaining is not implemented on Win64/MSVC. Otherwise 
 it should work(TM).
I was under the impression that both Trass3r and kink were getting random (?) EH-related crashes. I couldn't find any related issues on GitHub, though. David
There are crashes (e.h. unit tests core.thread, core.time) but I don't know if they are EH-related. The only way is to analyze and create bug reports. Regards, Kai
Oct 12 2014
parent reply "kink" <noone nowhere.com> writes:
I haven't run the unit tests yet (I'd be grateful if somebody 
could post the required command-line(s) - being able to run them 
via msbuild would obviously be luxurious). Current LDC head and 
LLVM head from yesterday can be built smoothly with MSVC 2013 
x64, and a hello-world program can then be built successfully, 
too - thanks guys.

But running

import std.stdio;
int main()
{
     writeln("Exception support?");
     try { throw new Exception("Exception support"); }
     catch (Exception e) { writeln(e.msg); }
     return 0;
}

yields an output such as:

Exception support?
Çu♠âý(Hë¤Hì

So yes, something seems to be working. ;) I'll try to dig deeper 
if I find the time.
Oct 12 2014
parent reply "Trass3r" <un known.com> writes:
Build with makefiles (hmm I've never tried ninja) and run make 
test resp. ctest -V -j <num>
Note that the unwind tables are untested.
Oct 12 2014
parent reply "kink" <noone nowhere.com> writes:
 Build with makefiles (hmm I've never tried ninja) and run make 
 test resp. ctest -V -j <num>
Thanks man, I'm giving ninja a go (single .exe as github release, very handy), parallel compilation at last! :) Looks like "ninja test" is still gonna take a while though using debug ldc2.exe. I'll update the Wiki page about how to run the tests if it works.
Oct 12 2014
parent reply "kink" <noone nowhere.com> writes:
The tests don't run with ninja, they really need make. Do I 
really have to install MinGW MSYS or does anyone know a better 
alternative?
Oct 13 2014
parent reply "Trass3r" <un known.com> writes:
On Monday, 13 October 2014 at 08:06:45 UTC, kink wrote:
 The tests don't run with ninja, they really need make. Do I 
 really have to install MinGW MSYS or does anyone know a better 
 alternative?
Only the dmd testsuite needs make. ninja is awesome, I also tested it :)
Oct 13 2014
parent "kink" <noone nowhere.com> writes:
 Only the dmd testsuite needs make.
Thanks for the hint. I had to fix a linking error in core.stdc.fenv (the global _FE_DFL_ENV has been renamed to _Fenv0 in MSVCRT 2013+) and then get ahold of curl.lib & dll to get the test-runners to compile first. My results are 82 segfaults: druntime & druntime-debug): 5 segfaults: * core.math * core.thread * core.time * ldc.longdouble * rt.lifetime phobos: 34 segfaults phobos-debug: 38 segfaults So about 80% of the modules passed all their unit tests.
Oct 14 2014
prev sibling parent reply "Trass3r" <un known.com> writes:
 Exception chaining is not implemented on Win64/MSVC. Otherwise 
 it should work(TM)
https://github.com/ldc-developers/ldc/issues/166#issuecomment-54522891
Oct 12 2014
next sibling parent "David Nadlinger" <code klickverbot.at> writes:
On Sunday, 12 October 2014 at 21:08:55 UTC, Trass3r wrote:
 Exception chaining is not implemented on Win64/MSVC. Otherwise 
 it should work(TM)
https://github.com/ldc-developers/ldc/issues/166#issuecomment-54522891
Thanks, I missed your comments there. David
Oct 12 2014
prev sibling parent "Kai Nacke" <kai redstar.de> writes:
On Sunday, 12 October 2014 at 21:08:55 UTC, Trass3r wrote:
 Exception chaining is not implemented on Win64/MSVC. Otherwise 
 it should work(TM)
https://github.com/ldc-developers/ldc/issues/166#issuecomment-54522891
Thanks for the hint. Obviously the exception object is not passed as expected. I'll look into this. Regards, Kai
Oct 13 2014
prev sibling parent reply "David Nadlinger" <code klickverbot.at> writes:
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
Oct 11 2014
next sibling parent "Trass3r" <un known.com> writes:
 This seems to affect LLVM 3.6 only.
Well you need the very latest version to get the EH fixes but yeah ;)
Oct 11 2014
prev sibling parent "Kai Nacke" <kai redstar.de> writes:
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
Oct 12 2014
prev sibling parent "Kai Nacke" <kai redstar.de> writes:
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
Oct 08 2014