LDC 1.1.0-beta3 has been released!
Disgreat via digitalmars-d-ldc
digitalmars-d-ldc at puremagic.com
Tue Oct 11 19:29:21 PDT 2016
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
* thread #1: tid = 0x3b8f, 0x00007fff8abc0fc4
libsystem_platform.dylib`_platform_memmove$VARIANT$Haswell + 164,
queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=2, address=0x100023ff7)
frame #0: 0x00007fff8abc0fc4
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.
More information about the digitalmars-d-ldc
mailing list