[ANNOUNCE] GHC 8.6.4 is now available

[Takenobu Tani]

Hi,

I always appreciate your hard work.

Perhaps you may know, but the following html documents are not included in
the windows tarball [1]:

  * doc/html/index.html
  * doc/html/users_guide/index.html
  * doc/html/libraries/index.html

These files were included in ghc-8.6.3 tarball [2].

These are very useful in offline or slow network environment :)


[1]:
https://downloads.haskell.org/ghc/8.6.4/ghc-8.6.4-x86_64-unknown-mingw32.tar.xz
[2]:
https://downloads.haskell.org/ghc/8.6.3/ghc-8.6.3-x86_64-unknown-mingw32.tar.xz

Regards,
Takenobu



On Wed, Mar 6, 2019 at 5:53 AM Ben Gamari <ben at well-typed.com> wrote:

>
> Hello everyone,
>
> The GHC team is very happy to announce the availability of GHC 8.6.4, a
> bugfix release in the GHC 8.6 series. The source distribution, binary
> distributions, and documentation for this release are available at
>
>     https://downloads.haskell.org/~ghc/8.6.4
>
> The 8.6.4 release fixes several regressions present in 8.6.3 including:
>
>  - A regression resulting in segmentation faults on Windows introduced
>    by the fix for #16071 backported in 8.6.3. This fix has been reverted,
>    meaning that 8.6.4 is once again susceptible to #16071. #16071 will
>    be fixed in GHC 8.8.1.
>
>  - A bug resulting in incorrect locking on Darwin, potentially resulting
>    in hangs at shutdown (#16150)
>
>  - A few bugs in the profiled runtime resulting in the potential for
>    memory unsafety has been fixed (#15508).
>
>  - The `process` and `transformers` libraries shipped now properly
>    reflect released Hackage releases (#16199)
>
>  - A bug where TH name resolution would break in a plugin context has
>    been fixed (#16104)
>
>  - Compilers that do not support TemplateHaskell no longer advertise
>    such support in `--supported-languages` (#16331)
>
> As a few of these issues are rather serious users are strongly
> encouraged to upgrade. See Trac [1] for a full list of issues resolved
> in this release.
>
> Note that this release ships with one significant but long-standing bug
> (#14251): Calls to functions taking both Float# and Double# may result
> in incorrect code generation when compiled using the LLVM code generator.
> This is not a new issue, it has existed as long as the LLVM code
> generator has existed; however, changes in code generation in 8.6 made
> it more likely that user code using only lifted types will trigger it.
>
> Note also that this is the first release cut from our (yet again)
> revamped continuous integration infrastructure. While we have done a
> great deal of checking to ensure that the build configuration reflects
> that of previous releases, do let us know if something looks off.
>
> Happy compiling!
>
> Cheers,
>
> - Ben
>
> [1]
> https://ghc.haskell.org/trac/ghc/query?status=closed&milestone=8.6.4&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20190306/ef14da24/attachment.html>