[Haskell-cafe] Fwd: [Haskell] [ANNOUNCE] GHC 8.6.2 is now available

[Dan Burton]

(fwd to the real haskell cafe list)

-- Dan Burton


---------- Forwarded message ---------
From: Dan Burton <danburton.email at gmail.com>
Date: Sat, Nov 10, 2018 at 11:30 AM
Subject: Re: [Haskell] [ANNOUNCE] GHC 8.6.2 is now available
To: Ben Gamari <ben at well-typed.com>
Cc: Haskell-cafe <haskell-cafe at googlegroups.com>


I have two trivialities to bring up:

1. Could you update https://downloads.haskell.org/~ghc/latest/ to point to
8.6.2? (It's currently showing 8.6.1.)
2. The SHA1SUMS and SHA256SUMS for 8.6.2 list a file
"./ghc-8.6.2-x86_64-darwin.tar.xz", but that is a broken link; the
corresponding file is found at "./ghc-8.6.2-x86_64*-apple*-darwin.tar.xz".
Can these be harmonized?

Thanks!

-- Dan Burton


On Mon, Nov 5, 2018 at 11:29 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.2, a
> bugfix release to GHC 8.6.1. The source distribution, binary
> distributions, and documentation for this release are available at
>
>     https://downloads.haskell.org/~ghc/8.6.2
>
> The 8.6 release fixes several regressions present in 8.6.1 including:
>
>  * A long-standing (but previously hard to manifest) bug resulting in
>    undefined behavior for some applications of dataToTag# has been fixed
>    (#15696)
>
>  * An incorrect linker path to libgmp in the Mac OS binary distributions
>    (#15404)
>
>  * A regression rendering Windows installations to read-only directories
>    unusable (#15667)
>
>  * A regression resulting in panics while compiling some record updates
>    of GADTs constructors  (#15499)
>
>  * A regression resulting in incorrect type errors when splicing types
>    into constraint contexts has been fixed (#15815)
>
>  * Around a dozen other issues.
>
> 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.
>
> Happy compiling!
>
> Cheers,
>
> - Ben
>
>
>
> [1]
> https://ghc.haskell.org/trac/ghc/query?status=closed&milestone=8.6.2&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority
> _______________________________________________
> Haskell mailing list
> Haskell at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-cafe/attachments/20181110/ac59640c/attachment.html>