Re: LDC 1.19.0

2019-12-26 Thread Joseph Rushton Wakeling via Digitalmars-d-announce
On Thursday, 26 December 2019 at 12:41:14 UTC, Joseph Rushton 
Wakeling wrote:

On Friday, 20 December 2019 at 18:30:37 UTC, H. S. Teoh wrote:

LLVM upgraded to v9.0.1, incl. experimental AVR backend.


Is that an upstream release?  I don't see a 9.0.1 in the LDC 
LLVM fork:

https://github.com/ldc-developers/llvm/releases


Oh, I see.  The details are covered in the LDC 1.19.0 release 
notes (there's a repo switch):

https://github.com/ldc-developers/ldc/releases/tag/v1.19.0


Re: LDC 1.19.0

2019-12-26 Thread Joseph Rushton Wakeling via Digitalmars-d-announce

On Friday, 20 December 2019 at 18:30:37 UTC, H. S. Teoh wrote:

LLVM upgraded to v9.0.1, incl. experimental AVR backend.


Is that an upstream release?  I don't see a 9.0.1 in the LDC LLVM 
fork:

https://github.com/ldc-developers/llvm/releases


Re: LDC 1.19.0

2019-12-20 Thread H. S. Teoh via Digitalmars-d-announce
On Fri, Dec 20, 2019 at 03:19:43PM +, kinke via Digitalmars-d-announce 
wrote:
> Glad to announce LDC 1.19:

Awesome!!  With every release, LDC is becoming more and more my go-to D
compiler.  Big thanks to all involved in making this happen!


T

-- 
A linguistics professor was lecturing to his class one day.
"In English," he said, "A double negative forms a positive. In some
languages, though, such as Russian, a double negative is still a
negative. However, there is no language wherein a double positive can
form a negative."
A voice from the back of the room piped up, "Yeah, yeah."


Re: LDC 1.19.0-beta2

2019-12-02 Thread kinke via Digitalmars-d-announce

On Sunday, 1 December 2019 at 19:11:53 UTC, Dennis wrote:
I have Visual Studio installed. How do I know which import 
libraries are being used?


Then you're most likely NOT using the MS toolchain, since it has 
to be explicitly enabled (see README.txt). - It can be verified 
by checking the DLL dependencies of generated binaries (e.g., 
dependency on ucrtbase.dll -> most likely NOT using MS toolchain) 
or linking with `-v` to check the linker cmdline (containing 
/LIBPATH:...\mingw -> NOT using MS toolchain).


I only had some issues with the old OMF ones, so I don't tend 
to use that target.


LDC doesn't and has never supported support OMF.


Re: LDC 1.19.0-beta2

2019-12-01 Thread Dennis via Digitalmars-d-announce

On Friday, 29 November 2019 at 20:55:10 UTC, kinke wrote:

Glad to announce the second beta for LDC 1.19.


Thanks!

with significant import library additions and changes. So if 
you target Windows and don't use the Microsoft toolchain, 
please participate in testing to prevent regressions for the 
final 1.19 release.


I have Visual Studio installed. How do I know which import 
libraries are being used? So far linking Windows libraries worked 
on COFF targets, so I never looked into them.
I only had some issues with the old OMF ones, so I don't tend to 
use that target.


Re: LDC 1.19.0-beta1

2019-11-09 Thread kinke via Digitalmars-d-announce

On Saturday, 9 November 2019 at 07:57:02 UTC, zoujiaqing wrote:

I mean you can waiting for dmd 2.089.1 to release ldc 1.9.0 : )


That's the plan anyway; plus this druntime regression most likely 
doesn't apply to LDC (atomics are highly compiler-specific).


To catch regressions like this earlier, it would certainly help 
if people used the beta compiler packages for their CI too; for 
Travis, it's as simple as adding additional jobs with `d: 
-beta`.


Re: LDC 1.19.0-beta1

2019-11-09 Thread zoujiaqing via Digitalmars-d-announce

On Friday, 8 November 2019 at 13:36:27 UTC, kinke wrote:


Please file a druntime issue, this is DMD.


Yes.
I mean you can waiting for dmd 2.089.1 to release ldc 1.9.0 : )

Thanks.


Re: LDC 1.19.0-beta1

2019-11-08 Thread kinke via Digitalmars-d-announce

On Friday, 8 November 2019 at 02:56:31 UTC, zoujiaqing wrote:

2.089.0 have bug ..

building hunt library error:
/home/travis/dlang/dmd-2.089.0/linux/bin64/../../src/druntime/import/core/atomic.d(293,64):
 Error: template core.internal.atomic.atomicCompareExchangeStrongNoResult 
cannot deduce function from argument types !(cast(MemoryOrder)5, 
cast(MemoryOrder)5)(IForkJoinTask*, IForkJoinTask, IForkJoinTask), candidates 
are:

all logs view:
https://travis-ci.org/huntlabs/hunt/jobs/607449502


Please file a druntime issue, this is DMD.


Re: LDC 1.19.0-beta1

2019-11-07 Thread zoujiaqing via Digitalmars-d-announce

On Tuesday, 5 November 2019 at 20:50:31 UTC, kinke wrote:

Glad to announce the first beta for LDC 1.19:

* Based on D 2.089.0.
* Slight codegen improvements, incl. a breaking extern(D) ABI 
change for Posix x86[_64] targets, and dead branch elimination 
for if statements with constant condition (in the hopes of 
possibly increasing compilation speed).

* Fixed misc. CMake issues with some LLVM 9 configurations.
* Default Posix linker driver is now `cc` instead of `gcc`.

Full release log and downloads: 
https://github.com/ldc-developers/ldc/releases/tag/v1.19.0-beta1


Please help test, and thanks to all contributors!


2.089.0 have bug ..

building hunt library error:
/home/travis/dlang/dmd-2.089.0/linux/bin64/../../src/druntime/import/core/atomic.d(293,64):
 Error: template core.internal.atomic.atomicCompareExchangeStrongNoResult 
cannot deduce function from argument types !(cast(MemoryOrder)5, 
cast(MemoryOrder)5)(IForkJoinTask*, IForkJoinTask, IForkJoinTask), candidates 
are:

all logs view:
https://travis-ci.org/huntlabs/hunt/jobs/607449502