X86_mscoff / x86_64 as default for dub projects (windows)

Andre Pany andre at s-e-a-p.de
Thu Dec 20 09:24:33 UTC 2018

On Wednesday, 19 December 2018 at 11:32:58 UTC, Andre Pany wrote:
> On Saturday, 8 December 2018 at 15:04:12 UTC, Guillaume Piolat 
> wrote:
>> On Friday, 7 December 2018 at 13:23:54 UTC, Andre Pany wrote:
>>> Visual studio is no longer needed as lld and x86mscoff/x86_64 
>>> libraries now included in dmd and LDC:)
>>> We just need to get it mature.
>>> Kind regards
>>> Andre
>> Is it any faster than OPTLINK?
> I had some tries. LLD link is very fast in my applications. It 
> feels even noticeable faster than OPTLINK.
> But also I facing some maturity issues.
> - While trying to run dub test in combination with dependency 
> d-unit and a module command.d containing an std.datetime import 
> there is always an linker error:
> Native PDB Error: The entry already exists.  The specified 
> module already exists
> I have a reduced test case (dustmite is great!) and will file 
> an issue
> - From time to time there is a spurious linker error:
> Error: module `NOLOGO` is in file '\NOLOGO.d' which cannot be 
> read
> I don't know how to reproduce this error but it disappears on 
> next try.
> Kind regards
> André

As pointed out by Kinke in issue 19503, dmd ships with an old 
lld-link version (v5.0.1).
Replacing it with v7.0 (already shipped with recent LDC) solves
the Native PDB Error.

(I have to update the issue 

The spurious NOLOGO problem still occurs on every 3 or 4 try for 
the same dmd linker command (generated by dub).

Kind regards

More information about the Digitalmars-d mailing list