Hi all!

I merged the merge-2.068 branch into master. The master branch now contains the code for next release 0.17.0, based on frontend release 2.068.2.

Again, please note that starting with this version we have drop support for LLVM versions 3.1 - 3.4. Travis-CI already reflects this.

You can expect a bugfix release 0.16.1 and next alpha 0.17.0-alpha1 soon.

Regards,
Kai

On 27 Oct 2015, at 23:27, Kai Nacke via digitalmars-d-ldc wrote:
> I merged the merge-2.068 branch into master. The master branch now contains the code for next release 0.17.0, based on frontend release 2.068.2.

Did you fix the remaining Travis build issues?

 — David

On Tuesday, 27 October 2015 at 21:27:15 UTC, Kai Nacke wrote:
> Hi all!
>
> I merged the merge-2.068 branch into master. The master branch now contains the code for next release 0.17.0, based on frontend release 2.068.2.
>
> Again, please note that starting with this version we have drop support for LLVM versions 3.1 - 3.4. Travis-CI already reflects this.
>
> You can expect a bugfix release 0.16.1 and next alpha 0.17.0-alpha1 soon.
>
> Regards,
> Kai

Wow, that was fast!

On Tuesday, 27 October 2015 at 21:32:41 UTC, David Nadlinger wrote:
> On 27 Oct 2015, at 23:27, Kai Nacke via digitalmars-d-ldc wrote:
>> I merged the merge-2.068 branch into master. The master branch now contains the code for next release 0.17.0, based on frontend release 2.068.2.
>
> Did you fix the remaining Travis build issues?

I made it even worse: LLVM 3.8 and OS X are now part of the Travis CI game.

Regards,
Kai

On 28 Oct 2015, at 10:02, Kai Nacke via digitalmars-d-ldc wrote:
> I made it even worse: LLVM 3.8 and OS X are now part of the Travis CI game.

At least those don't break the build. ;)

 — David

On Tuesday, 27 October 2015 at 21:27:15 UTC, Kai Nacke wrote:
> Hi all!
>
> I merged the merge-2.068 branch into master. The master branch now contains the code for next release 0.17.0, based on frontend release 2.068.2.
>
> Again, please note that starting with this version we have drop support for LLVM versions 3.1 - 3.4. Travis-CI already reflects this.
>
> You can expect a bugfix release 0.16.1 and next alpha 0.17.0-alpha1 soon.
>
> Regards,
> Kai

Congratulations! Looking forward to testing it :)

On Tuesday, 27 October 2015 at 21:27:15 UTC, Kai Nacke wrote:
> Hi all!
>
> I merged the merge-2.068 branch into master. The master branch now contains the code for next release 0.17.0, based on frontend release 2.068.2.
>
> Again, please note that starting with this version we have drop support for LLVM versions 3.1 - 3.4. Travis-CI already reflects this.
>
> You can expect a bugfix release 0.16.1 and next alpha 0.17.0-alpha1 soon.
>
> Regards,
> Kai

Awesome! You guys rock!

When is your book coming out ?

--Stephan

On Thursday, 29 October 2015 at 09:56:52 UTC, extrawurst wrote:
> On Tuesday, 27 October 2015 at 21:27:15 UTC, Kai Nacke wrote:
>> Hi all!
>>
>> I merged the merge-2.068 branch into master. The master branch now contains the code for next release 0.17.0, based on frontend release 2.068.2.
>>
>> Again, please note that starting with this version we have drop support for LLVM versions 3.1 - 3.4. Travis-CI already reflects this.
>>
>> You can expect a bugfix release 0.16.1 and next alpha 0.17.0-alpha1 soon.
>>
>> Regards,
>> Kai
>
> Awesome! You guys rock!
>
> When is your book coming out ?

It depends on me. I still need to rework some chapters.

Regards,
Kai

http://ldc.acomirei.ru/ is up with latest ldc + llvm
Sorry for such a long down. Was busy.

On Saturday, 14 November 2015 at 21:08:14 UTC, Temtaime wrote:
> http://ldc.acomirei.ru/ is up with latest ldc + llvm
> Sorry for such a long down. Was busy.

http://goo.gl/OW6YUp

Also i wonder why ldc does not generate vfmadd132ss instruction like as gcc do ?