Re: [ANNOUNCE] GHC 8.6.1 released

[Ben Gamari]

On September 24, 2018 2:09:13 AM CDT, Jens Petersen  
wrote:
>I have built 8.6.1 for Fedora 27, 28, 29, Rawhide, and EPEL7 in:
>
>https://copr.fedorainfracloud.org/coprs/petersen/ghc-8.6.1/
>
>The repo also includes latest cabal-install.
>
Thanks Jens! This is a very helpful service. 

Cheers, 

- Ben 


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

RE: Windows testsuite failures

[Simon Peyton Jones via ghc-devs]

Tamar

Thank you, that’s great!

For the ones that need more work, can we mark them as expect-broken, so that 
they don’t pollute the testsuite output?

Simon


From: loneti...@gmail.com 
Sent: 24 September 2018 07:13
To: Simon Peyton Jones 
Subject: RE: Windows testsuite failures


Hi Simon,

I created some patches to fix the majority of these

https://phabricator.haskell.org/D5174
https://phabricator.haskell.org/D5175
https://phabricator.haskell.org/D5176

The remaining ones I’ve either pinged the patches that caused the issues or 
created tickets
For them because they’re actual bugs that require a bit more time to find the 
cause and fix.

https://ghc.haskell.org/trac/ghc/ticket/15668
https://ghc.haskell.org/trac/ghc/ticket/15669
https://ghc.haskell.org/trac/ghc/ticket/15670
https://ghc.haskell.org/trac/ghc/ticket/15671

these should bring down the amount of failing tests to about 5.

Kind Regards,
Tamar

From: Simon Peyton Jones
Sent: Thursday, September 20, 2018 12:05
To: Phyx
Subject: RE: Windows testsuite failures

Thanks Tamar.  I’ll look forward to hearing back

S

From: Phyx mailto:loneti...@gmail.com>>
Sent: 20 September 2018 12:02
To: Simon Peyton Jones mailto:simo...@microsoft.com>>
Cc: ghc-devs@haskell.org
Subject: Re: Windows testsuite failures

Hi Simon,

Thanks for the email. I haven't been building head much as I'm working on top 
of some older commits. From a quick look it seems like the plugin ones are 
probably testisms, the plugins aren't found so likely a missing path entry 
somewhere.

The linker ones are are weird, I'll need to take a closer look at those, likely 
culprit is my recent patch, I had been testing in the 32 bit build and didn't 
notice these.

There are a few worrying segfault that shouldn't be there on some random tests 
so I'll take a closer look at those too.

And the stat changes need to be updated.

The framework failures I don't see on harbormaster, so think they are again a 
threading artifact. Need to figure out a more effective way to debug these to 
find a permanent fix. The ones that harbormaster does see are encoding related. 
touch is failing on non-ascii names.

I will take a look this weekend.

Kind regards,
Tamar

On Thu, Sep 20, 2018, 11:33 Simon Peyton Jones 
mailto:simo...@microsoft.com>> wrote:
Hi Tamar
The list of testsuite failure on Windows has grown quite long – see below.  
Most seem to concern plugins or linking.
Do you know what is going on here?  If they can’t be fixed, can we mark them as 
expect_broken on Windows, so that it’s easier (when developing) to know when 
I’ve introduced a regression.  Currently I have to do a manual diff against a 
rather long list.
Thanks!
Simon


SUMMARY for test run started at Thu Sep 20 00:13:20 2018 GMTST

1:03:11 spent to go through

6530 total tests, which gave rise to

   18728 test cases, of which

   12206 were skipped



  33 had missing libraries

6278 expected passes

 173 expected failures



   9 caused framework failures

   1 caused framework warnings

   0 unexpected passes

  31 unexpected failures

   7 unexpected stat failures



Unexpected failures:

   ghci/linking/dyn/T10955dyn.run  T10955dyn [bad exit code] (normal)

   ghci/linking/dyn/T10955.run T10955 [bad stderr] (ghci)

   ghci/linking/dyn/T11072gcc.run  T11072gcc [bad exit code] (normal)

   numeric/should_run/FloatFnInverses.run  FloatFnInverses [bad stdout] (normal)

   plugins/T11244.run  T11244 [bad stderr] (normal)

   plugins/plugin-recomp-change.runplugin-recomp-change [bad exit code] 
(normal)

   rts/T7040_ghci.run  T7040_ghci [bad stdout] (ghci)

   rts/linker_unload.run   linker_unload [bad exit code] 
(normal)

   rts/linker_error1.run   linker_error1 [bad exit code] 
(normal)

   rts/linker_error2.run   linker_error2 [bad exit code] 
(normal)

   rts/T12771/T12771.run   T12771 [bad exit code] (normal)

   rts/T13082/T13082_good.run  T13082_good [bad exit code] (normal)

   rts/T14611/T14611.run   T14611 [bad exit code] (normal)

   simplCore/should_compile/T7702.run  T7702 [exit code non-0] (normal)

   rts/T10672/T10672_x64.run   T10672_x64 [bad exit code] (normal)

   libraries/Win32/tests/T4452.run T4452 [bad exit code] (normal)

   plugins/plugins01.run   plugins01 [bad exit code] (normal)

   plugins/plugins07.run   plugins07 [bad exit code] (normal)

   plugins/plugins09.run   plugins09 [bad exit code] (normal)

   plugins/plugins11.run   plugins11 [bad exit code] (normal)

   plugins/plugins12.run   plugins12 [bad exit code] (normal)

   plugins/plugins13.run   plugins13 [bad exit code] (normal)

   

clonetype

[Harendra Kumar]

Often, we need to create a newtype that is equivalent to a given type for
safety reasons. Using type  synonym is useless from type safety
perspective. With newtype, we have to add a "deriving" clause to it for
deriving the required instances, to make it practically useful.

Does it make sense, and is it possible to have something like a "clonetype"
that creates a new type and derives all the instances of the parent type as
well? It will be quite helpful in creating equivalent newtype synonyms
quickly. Almost always, I do not use a newtype where I should just because
of the inconvenience of deriving the instances. Ideally, we should just be
able to say something like:

clonetype MyString = String

and we are good to go.  What is the shortest possible way to achieve this
with currently available mechanisms, if any?

-harendra
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [ANNOUNCE] GHC 8.6.1 released

[Jens Petersen]

I have built 8.6.1 for Fedora 27, 28, 29, Rawhide, and EPEL7 in:

https://copr.fedorainfracloud.org/coprs/petersen/ghc-8.6.1/

The repo also includes latest cabal-install.

Thanks for the release!
Jens
On Sat, 22 Sep 2018 at 09:58, Ben Gamari  wrote:
>
> Hello everyone,
>
> The GHC team is pleased to announce the availability of GHC 8.6.1, the
> fourth major release in the GHC 8 series. The source distribution, binary
> distributions, and documentation for this release are available at
>
> https://downloads.haskell.org/~ghc/8.6.1
>
> The 8.6 release fixes over 400 bugs from the 8.4 series and introduces a
> number of exciting features. These most notably include:
>
>  * A new deriving mechanism, `deriving via`, providing a convenient way
>for users to extend Haskell's typeclass deriving mechanism
>
>  * Quantified constraints, allowing forall quantification in constraint 
> contexts
>
>  * An early version of the GHCi `:doc` command
>
>  * The `ghc-heap-view` package, allowing introspection into the
>structure of GHC's heap
>
>  * Valid hole fit hints, helping the user to find terms to fill typed
>holes in their programs
>
>  * The BlockArguments extension, allowing the `$` operator to be omitted
>in some unambiguous contexts
>
>  * An exciting new plugin mechanism, source plugins, allowing plugins to
>inspect and modify a wide variety of compiler representations.
>
>  * Improved recompilation checking when plugins are used
>
>  * Significantly better handling of macOS linker command size limits,
>avoiding linker errors while linking large projects
>
>  * The next phase of the MonadFail proposal, enabling
>-XMonadFailDesugaring by default
>
> A full list of the changes in this release can be found in the
> release notes:
>
> 
> https://downloads.haskell.org/~ghc/8.6.1/docs/html/users_guide/8.6.1-notes.html
>
> Perhaps of equal importance, GHC 8.6 is the second major release made
> under GHC's accelerated six-month release schedule and the first set of
> binary distributions built primarily using our new continuous
> integration scheme. While the final 8.6 release is around three weeks
> later than initially scheduled due to late-breaking bug reports, we
> expect that the 8.8 release schedule shouldn't be affected.
>
> Thanks to everyone who has contributed to developing, documenting, and
> testing this release!
>
> As always, let us know if you encounter trouble.
>
>
> How to get it
> ~
>
> The easy way is to go to the web page, which should be self-explanatory:
>
> https://www.haskell.org/ghc/
>
> We supply binary builds in the native package format for many
> platforms, and the source distribution is available from the same
> place.
>
> Packages will appear as they are built - if the package for your
> system isn't available yet, please try again later.
>
>
> Background
> ~~
>
> Haskell is a standard lazy functional programming language.
>
> GHC is a state-of-the-art programming suite for Haskell.  Included is
> an optimising compiler generating efficient code for a variety of
> platforms, together with an interactive system for convenient, quick
> development.  The distribution includes space and time profiling
> facilities, a large collection of libraries, and support for various
> language extensions, including concurrency, exceptions, and foreign
> language interfaces. GHC is distributed under a BSD-style open source license.
>
> A wide variety of Haskell related resources (tutorials, libraries,
> specifications, documentation, compilers, interpreters, references,
> contact information, links to research groups) are available from the
> Haskell home page (see below).
>
>
> On-line GHC-related resources
> ~~
>
> Relevant URLs on the World-Wide Web:
>
> GHC home page  https://www.haskell.org/ghc/
> GHC developers' home page  https://ghc.haskell.org/trac/ghc/
> Haskell home page  https://www.haskell.org/
>
>
> Supported Platforms
> ~~~
>
> The list of platforms we support, and the people responsible for them,
> is here:
>
>https://ghc.haskell.org/trac/ghc/wiki/Contributors
>
> Ports to other platforms are possible with varying degrees of
> difficulty.  The Building Guide describes how to go about porting to a
> new platform:
>
> https://ghc.haskell.org/trac/ghc/wiki/Building
>
>
> Developers
> ~~
>
> We welcome new contributors.  Instructions on accessing our source
> code repository, and getting started with hacking on GHC, are
> available from the GHC's developer's site run by Trac:
>
>   https://ghc.haskell.org/trac/ghc/
>
>
> Mailing lists
> ~
>
> We run mailing lists for GHC users and bug reports; to subscribe, use
> the web interfaces at
>
> https://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-tickets
>
> There are several other haskell and ghc-related mailing