[Git][ghc/ghc][wip/marge_bot_batch_merge_job] 10 commits: Compute demand signatures assuming idArity

[Marge Bot]

 Marge Bot pushed to branch wip/marge_bot_batch_merge_job at Glasgow Haskell Compiler / GHC


Commits:
3e96c4d7 by Sebastian Graf at 2019-04-30T14:02:24Z
Compute demand signatures assuming idArity

This does four things:

1. Look at `idArity` instead of manifest lambdas to decide whether to use LetUp
2. Compute the strictness signature in LetDown assuming at least `idArity`
   incoming arguments
3. Remove the special case for trivial RHSs, which is subsumed by 2
4. Don't perform the W/W split when doing so would eta expand a binding.
   Otherwise we would eta expand PAPs, causing unnecessary churn in the
   Simplifier.

NoFib Results

--------------------------------------------------------------------------------
        Program         Allocs    Instrs
--------------------------------------------------------------------------------
 fannkuch-redux          +0.3%      0.0%
             gg          -0.0%     -0.1%
       maillist          +0.2%     +0.2%
        minimax           0.0%     +0.8%
         pretty           0.0%     -0.1%
        reptile          -0.0%     -1.2%
--------------------------------------------------------------------------------
            Min          -0.0%     -1.2%
            Max          +0.3%     +0.8%
 Geometric Mean          +0.0%     -0.0%

- - - - -
dd696a6a by Alp Mestanogullari at 2019-04-30T14:02:26Z
Build Hadrian with -Werror in the 'ghc-in-ghci' CI job

- - - - -
8e84eeff by Ben Gamari at 2019-04-30T14:02:26Z
ErrUtils: Emit progress messages to eventlog

- - - - -
b3264df5 by Ben Gamari at 2019-04-30T14:02:26Z
Emit GHC timing events to eventlog

- - - - -
6e7b6f6f by Chaitanya Koparkar at 2019-04-30T14:02:28Z
Fix #16593 by having only one definition of -fprint-explicit-runtime-reps

[skip ci]

- - - - -
3e691156 by Sven Tennie at 2019-04-30T14:02:29Z
Typeset Big-O complexities with Tex-style notation (#16090)

Use `\min` instead of `min` to typeset it as an operator.

- - - - -
933e759a by Shayne Fletcher at 2019-04-30T14:02:31Z
Make Extension derive Bounded

- - - - -
7d599bbf by Ben Gamari at 2019-04-30T14:02:31Z
testsuite: Mark concprog001 as fragile

Due to #16604.
- - - - -
f34d6576 by Alp Mestanogullari at 2019-04-30T14:02:32Z
Hadrian: generate JUnit testsuite report in Linux CI job

We also keep it as an artifact, like we do for non-Hadrian jobs, and list it
as a junit report, so that the test results are reported in the GitLab UI for
merge requests.

- - - - -
7c7eb687 by Vladislav Zavialov at 2019-04-30T14:02:33Z
Pattern/expression ambiguity resolution

This patch removes 'EWildPat', 'EAsPat', 'EViewPat', and 'ELazyPat'
from 'HsExpr' by using the ambiguity resolution system introduced
earlier for the command/expression ambiguity.

Problem: there are places in the grammar where we do not know whether we
are parsing an expression or a pattern, for example:

	do { Con a b <- x } -- 'Con a b' is a pattern
	do { Con a b }      -- 'Con a b' is an expression

Until we encounter binding syntax (<-) we don't know whether to parse
'Con a b' as an expression or a pattern.

The old solution was to parse as HsExpr always, and rejig later:

	checkPattern :: LHsExpr GhcPs -> P (LPat GhcPs)

This meant polluting 'HsExpr' with pattern-related constructors. In
other words, limitations of the parser were affecting the AST, and all
other code (the renamer, the typechecker) had to deal with these extra
constructors.

We fix this abstraction leak by parsing into an overloaded
representation:

	class DisambECP b where ...
	newtype ECP = ECP { runECP_PV :: forall b. DisambECP b => PV (Located b) }

See Note [Ambiguous syntactic categories] for details.

Now the intricacies of parsing have no effect on the hsSyn AST when it
comes to the expression/pattern ambiguity.

- - - - -


26 changed files:

- .gitlab-ci.yml
- compiler/basicTypes/Demand.hs
- compiler/basicTypes/Id.hs
- compiler/basicTypes/IdInfo.hs
- compiler/basicTypes/Var.hs
- compiler/coreSyn/CoreArity.hs
- compiler/coreSyn/CoreLint.hs
- compiler/coreSyn/CoreUnfold.hs
- compiler/deSugar/DsExpr.hs
- compiler/hieFile/HieAst.hs
- compiler/hsSyn/HsExpr.hs
- compiler/hsSyn/HsExtension.hs
- compiler/main/ErrUtils.hs
- compiler/parser/Lexer.x
- compiler/parser/Parser.y
- compiler/parser/RdrHsSyn.hs
- compiler/rename/RnExpr.hs
- compiler/simplCore/SimplMonad.hs
- compiler/simplCore/SimplUtils.hs
- compiler/stranal/DmdAnal.hs
- compiler/stranal/WorkWrap.hs
- compiler/stranal/WwLib.hs
- compiler/typecheck/TcRnTypes.hs
- docs/users_guide/glasgow_exts.rst
- docs/users_guide/using.rst
- + hadrian/ci.project


The diff was not included because it is too large.


View it on GitLab: https://gitlab.haskell.org/ghc/ghc/compare/8bd286b677a75a1164986daea7948fd907f1dd2a...7c7eb687a18cd6f2cb53a85096faae3cfc8e6676

-- 
View it on GitLab: https://gitlab.haskell.org/ghc/ghc/compare/8bd286b677a75a1164986daea7948fd907f1dd2a...7c7eb687a18cd6f2cb53a85096faae3cfc8e6676
You're receiving this email because of your account on gitlab.haskell.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-commits/attachments/20190430/c95c7348/attachment-0001.html>