www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.ldc - LDC 1.1.0-beta3 has been released!

reply Kai Nacke <kai redstar.de> writes:
Hi everyone!

On behalf of the LDC team I am proud to announce the new 
1.1.0-beta3 release!
It is based on the 2.071.2 front-end and supports LLVM 3.5-3.9.

As usual this beta3 release contains a lot of bug fixes. :-)

Please be aware that the command line interface was changed: See 
http://forum.dlang.org/post/ubobkfmsspbsmjunosna forum.dlang.org

Be sure to read the change log at the GitHub release page which 
also has the package download links:
https://github.com/ldc-developers/ldc/releases/tag/v1.1.0-beta3

MD5 checksums for the release packages:

7d796d7195df23a44136bd2ea74d23f3 ldc-1.1.0-beta3-src.tar.gz
983f016125548bd5abf268e4214896ab 
ldc2-1.1.0-beta3-freebsd-x86_64.tar.xz
87139908d773014df83d5e496f9eea49 
ldc2-1.1.0-beta3-linux-armv7hf.tar.xz
8d88533743783e8593b322e90fabaea7 
ldc2-1.1.0-beta3-linux-x86_64.tar.xz
21a3ddf18f63288a8dc021f9b7a6f5e9 ldc2-1.1.0-beta3-linux-x86.tar.xz
b1331db8fdd9900993e6f81be4c7218b 
ldc2-1.1.0-beta3-osx-x86_64.tar.xz
fb6fd2641fdbb65c4a357af24271f202 ldc2-1.1.0-beta3-win32-msvc.zip
cf52ec2722e8907b4c27efd281d25d2c ldc2-1.1.0-beta3-win64-msvc.zip

Regarding the binaries:
The Linux x86/x86_64 binaries are built on Ubuntu 12.04 LTS with 
gcc 4.8.x, ldc2 1.1.0-beta3 and LLVM 3.9.0. They work on Ubuntu 
12.04 LTS (or later) without installing additional software.
The Linux armv7hf binary is built on Gentoo/ARM with gcc 4.9.x, 
ldc2 ldc2 1.1.0-beta3 and LLVM 3.9.0.

The OS X binaries are built with LLVM 3.9.0 on OS X 10.10 and 
requires at least OS X 10.8.

The FreeBSD binaries are built on PC-BSD 10.3 with gcc 4.8.5, 
ldc2 1.1.0-beta3 and LLVM 3.9.0.

The Win32 and Win64 MSVC versions are built with VS2015 (update 
2) using ldc2 1.1.0-beta3 and LLVM 3.9.0 in release mode. The 
distribution now contains a precompiled libcurl 7.46.0 from 
http://d.darktech.org/libcurl.html. For any other VisualStudio 
version you need to rebuild the library.
You find the build script here: 
https://github.com/ldc-developers/ldc-scripts/blob/master/ldc2-win64/RELEASE.proj

Please be sure to report any bugs at 
https://github.com/ldc-developers/ldc/issues, and feel free to 
drop by at the digitalmars.D.ldc forums 
(http://forum.dlang.org/group/digitalmars.D.ldc) for any 
questions or comments.

Thanks to everybody involved in making this happen!

Regards,
Kai
Oct 09 2016
parent reply David Nadlinger via digitalmars-d-ldc <digitalmars-d-ldc puremagic.com> writes:
On 9 Oct 2016, at 13:30, Kai Nacke via digitalmars-d-ldc wrote:

 The OS X binaries are built with LLVM 3.9.0 on OS X 10.10 and requires 
 at least OS X 10.8.


I believe this still applies: 
https://github.com/ldc-developers/ldc/issues/1512

  — David
Oct 09 2016
parent reply Guillaume Piolat <first.last gmail.com> writes:
On Sunday, 9 October 2016 at 12:50:50 UTC, David Nadlinger wrote:

 On 9 Oct 2016, at 13:30, Kai Nacke via digitalmars-d-ldc wrote:

 The OS X binaries are built with LLVM 3.9.0 on OS X 10.10 and 
 requires at least OS X 10.8.


 I believe this still applies: 
 https://github.com/ldc-developers/ldc/issues/1512

  — David


Does it have any impact on generated binaries? Supporting 10.7 
still?
Oct 10 2016
parent reply David Nadlinger via digitalmars-d-ldc <digitalmars-d-ldc puremagic.com> writes:
Hi Guillaume,

On 10 Oct 2016, at 9:22, Guillaume Piolat via digitalmars-d-ldc wrote:

 Does it have any impact on generated binaries? Supporting 10.7 still?


It does have an impact on the generated binaries; the cause is a bug in 
ld. As long as the ld used to compile the D executable is new enough, 
the target system shouldn't matter.

  — David
Oct 11 2016
parent Disgreat <nomail nomail.com> writes:
On Tuesday, 11 October 2016 at 16:26:56 UTC, David Nadlinger 
wrote:

 Hi Guillaume,

 On 10 Oct 2016, at 9:22, Guillaume Piolat via digitalmars-d-ldc 
 wrote:

 Does it have any impact on generated binaries? Supporting 10.7 
 still?


 It does have an impact on the generated binaries; the cause is 
 a bug in ld. As long as the ld used to compile the D executable 
 is new enough, the target system shouldn't matter.

  — David


with DMD v2.071.2 MACOSX 10.11.6,  DUB -b release generate code 
quit with

```sh
(lldb) target create "./xwall-event"
2016-10-12 11:25:25.898 lldb[660:15239] Metadata.framework 
[Error]: couldn't get the client port
Current executable set to './xwall-event' (x86_64).
(lldb) run
Process 662 launched: './xwall-event' (x86_64)
Process 662 stopped

libsystem_platform.dylib`_platform_memmove$VARIANT$Haswell + 164, 
queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS 
(code=2, address=0x100023ff7)

libsystem_platform.dylib`_platform_memmove$VARIANT$Haswell + 164
libsystem_platform.dylib`_platform_memmove$VARIANT$Haswell:
->  0x7fff8abc0fc4 <+164>: movq   %rcx, (%rdi)
     0x7fff8abc0fc7 <+167>: movq   %r8, (%rdi,%rdx)
     0x7fff8abc0fcb <+171>: popq   %rbp
     0x7fff8abc0fcc <+172>: retq
```

on linux it quit with
```sh
Starting program: /root/projects/xwall/event/xwall-event
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x0000000000445b49 in gc.gc.GC.reallocNoSync() ()
```

this project run fine without "-b release",   and run fine with 
dmd or LDC 1.1.0 beta 2.

it is huge and I am not able to reduce it to simple code.
Oct 11 2016