<div dir="ltr"><div dir="ltr"><div>Hi Andreas,</div><div><br></div><div>GHC 8.6.4 not supporting profiling libs was the first thing mentioned in the release email</div><div><br></div><div>
- A regression resulting in segmentation faults on Windows introduced<br>
by the fix for #16071 backported in 8.6.3. This fix has been reverted,<br>
meaning that 8.6.4 is once again susceptible to #16071. #16071 will<br>
be fixed in GHC 8.8.1. <br></div><div><br></div><div>It was also stated that it would be back in 8.8.1. At this point there was no way to get profiling libs</div><div>on 8.6.x without a major backport of linker changes from master. The choice was made to revert the</div><div>change and release 8.6.4 without profiling libraries because of a stack allocation bug that was dormant for</div><div>years but completely killed the 32 bit distribution. That said the changelog linked to the wrong issue, the second</div><div>two should have been #15934 but that's not hard to figure out by looking at the ticket.<br></div><div><br></div><div>This was not an oversight, both the choice to release GHC 8.6.4 without profiling libs (which really to the average user is not mission critical)</div><div>and the fact to release 8.6.4 at all were thought out decisions. It could have been communicated better yes.</div><div><br></div><div>That 8.6.3 wasn't removed I don't know. I pulled it from chocolatey at least.</div><div><br></div><div>8.6 is more production ready than 8.4 was, it just doesn't support profiling libs for a while till 8.8 yes.</div><div><br></div><div>Tamar.<br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 19, 2019 at 5:57 PM Andreas Klebinger <<a href="mailto:klebinger.andreas@gmx.at">klebinger.andreas@gmx.at</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
Hello Devs,<br>
<br>
After running into #16408 today I realized there is as of yet no
released bindist<br>
of the 8.6 series which I would consider stable for windows.<br>
<br>
GHC 8.6.1 and 8.6.2 had a series of critical bugs which applied to
multiple platforms: <a class="gmail-m_227394233161228008moz-txt-link-freetext" href="https://gitlab.haskell.org/ghc/ghc/issues/16408" target="_blank">https://gitlab.haskell.org/ghc/ghc/issues/16408</a><br>
GHC 8.6.3 loops forever if compiling certain code using TH on windows.
This affects some very popular hackage packages: (<a href="https://gitlab.haskell.org/ghc/ghc/issues/16057" style="color:rgb(46,46,46);text-decoration:none;background-color:transparent" target="_blank">#16057)</a><br>
GHC 8.6.4 (marked stable) currently ships without profiling libraries,
making profiling impossible.<br>
<br>
Being stuck with 8.4 is one thing, and if properly communicated not too
bad.<br>
But it requires work to even find out about these (major) issues and to
discover that 8.6 is NOT production ready for windows.<br>
<br>
We offered the broken 8.6.3 as stable for weeks without any indication
that it was broken.<br>
We still serve GHC 8.6.4 as stable without any hint about the missing
profiling libraries.<br>
<br>
I can't offer solutions in this case but I feel like something about the
release management has to change if .<br>
Having to check the GHC bugtracker to find out if the current stable
release is actually stable is just not sustainable.<br>
<br>
<br>
<br>
<br>
</div>
_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org" target="_blank">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br>
</blockquote></div>