summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Restore the --coerce option in 'happy' configurationwip/happy-coerceVladislav Zavialov2019-05-115-8/+7
| | | | | | happy-1.19.10 has been released with a fix for --coerce in the presence of higher rank types. This should result in about 10% performance improvement in the parser.
* Add regression test case for old issue #493Kevin Buhr2019-05-105-0/+62
|
* gitlab-ci: Disable cleanup job on WindowsBen Gamari2019-05-101-27/+10
| | | | | | | As discussed in the Note, we now have a cron job to handle this and the cleanup job itself is quite fragile. [skip ci]
* Hadrian: programs need registered ghc-pkg librariesDavid Eichmann2019-05-105-8/+121
| | | | | | | | In Hadrian, building programs (e.g. `ghc` or `haddock`) requires libraries located in the ghc-pkg package database i.e. _build/stage1/lib/x86_64-linux-ghc-8.9.0.20190430/libHSdeepseq-1.4.4.0-ghc8.9.0.20190430.so Add the corresponding `need`s for these library files and the subsequent rules.
* Fix bugs and documentation for #13456Roland Senn2019-05-107-32/+68
|
* Add Generic tuple instances up to 15-tupleOleg Grenrus2019-05-101-0/+48
| | | | | | | | Why 15? Because we have Eq instances up to 15. Metric Increase: T9630 haddock.base
* Add a regression test for #14548Vladislav Zavialov2019-05-083-0/+28
|
* Add regression test for old issue #507Kevin Buhr2019-05-083-0/+3
|
* Purge TargetPlatform_NAME and cTargetPlatformStringJohn Ericson2019-05-086-10/+8
|
* Regression test for #16627.Richard Eisenberg2019-05-083-0/+21
| | | | test: typecheck/should_fail/T16627
* Print PAP object address in stg_PAP_info entry codeÖmer Sinan Ağacan2019-05-081-1/+1
| | | | Continuation to ce23451c
* stg_floatToWord32zh: zero-extend the Word32 (#16617)Kevin Buhr2019-05-085-2/+23
| | | | | | | The primop stgFloatToWord32 was sign-extending the 32-bit word, resulting in weird negative Word32s. Zero-extend them instead. Closes #16617.
* Implement ImportQualifiedPostShayne Fletcher2019-05-0825-42/+206
|
* Fix #16632 by using the correct SrcSpan in checkTyClHdrRyan Scott2019-05-084-2/+14
| | | | | | `checkTyClHdr`'s case for `HsTyVar` was grabbing the wrong `SrcSpan`, which lead to error messages pointing to the wrong location. Easily fixed.
* Fix #16603 by documenting some important changes in changelogsRyan Scott2019-05-082-0/+51
| | | | | | This addresses some glaring omissions from `libraries/base/changelog.md` and `docs/users_guide/8.8.1-notes.rst`, fixing #16603 in the process.
* Add regression test for old typechecking issue #505Kevin Buhr2019-05-072-1/+16
|
* Check for duplicate variables in associated default equationsRyan Scott2019-05-076-15/+81
| | | | | | | | | | | | | | | | A follow-up to !696's, which attempted to clean up the error messages for ill formed associated type family default equations. The previous attempt, !696, forgot to account for the possibility of duplicate kind variable arguments, as in the following example: ```hs class C (a :: j) where type T (a :: j) (b :: k) type T (a :: k) (b :: k) = k ``` This patch addresses this shortcoming by adding an additional check for this. Fixes #13971 (hopefully for good this time).
* Add /includes/dist to .gitignoreRyan Scott2019-05-071-0/+1
| | | | | | | | | As of commit d37d91e9a444a7822eef1558198d21511558515e, the GHC build now autogenerates a `includes/dist/build/settings` file. To avoid dirtying the current `git` status, this adds `includes/dist` to `.gitignore`. [ci skip]
* Hadrian: override $(ghc-config-mk), to prevent redundant config generationAlp Mestanogullari2019-05-062-0/+10
| | | | | | | | | | | | This required making the 'ghc-config-mk' variable overridable in testsuite/mk/boilerplate.mk, and then making use of this in hadrian to point to '<build root>/test/ghcconfig' instead, which is where we always put the test config. Previously, we would build ghc-config and run it against the GHC to be tested, a second time, while we're running the tests, because some include testsuite/mk/boilerplate.mk. This was causing unexpected output failures.
* Enable external interpreter when TH is requested but no internal interpreter ↵Alp Mestanogullari2019-05-061-2/+9
| | | | is available
* Remove `$(TOP)/ANNOUNCE` fileTakenobu Tani2019-05-061-131/+0
| | | | | | | | | Remove `$(TOP)/ANNOUNCE` because maintaining this file is expensive for each release. Currently, release announcements of ghc are made on ghc blogs and wikis. [skip ci]
* Remove cGhcEnableTablesNextToCodeJohn Ericson2019-05-065-15/+15
| | | | Get "Tables next to code" from the settings file instead.
* 'warnSpaceAfterBang' only in patterns (#16619)Vladislav Zavialov2019-05-055-24/+30
|
* Fix #16593 by having only one definition of -fprint-explicit-runtime-repsChaitanya Koparkar2019-05-052-23/+11
| | | | [skip ci]
* [ typo ] 'castFloatToWord32' -> 'castFloatToWord64'gallais2019-05-041-1/+1
| | | Probably due to a copy/paste gone wrong.
* Fix typo in 8.8.1 notes related to traceBinaryEventiustin2019-05-041-2/+3
| | | | - fixes double mention of `traceBinaryEvent#` (the second one should be `traceEvent#`, I think) - fixes note about `traceEvent#` taking a `String` - the docs say it takes a zero-terminated ByteString.
* PrimOps.cmm: remove unused stuffÖmer Sinan Ağacan2019-05-031-6/+2
|
* StgCmmMonad: remove emitProc_, don't export emitProcÖmer Sinan Ağacan2019-05-031-10/+6
|
* rts: Properly free the RTSSummaryStats structureÖmer Sinan Ağacan2019-05-031-6/+4
| | | | | | | | `stat_exit` always allocates a `RTSSummaryStats` but only sometimes frees it, which casues leaks. With this patch we unconditionally free the structure, fixing the leak. Fixes #16584
* Make equality constraints in kinds invisibleRyan Scott2019-05-0312-16/+100
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Issues #12102 and #15872 revealed something strange about the way GHC handles equality constraints in kinds: it treats them as _visible_ arguments! This causes a litany of strange effects, from strange error messages (https://gitlab.haskell.org/ghc/ghc/issues/12102#note_169035) to bizarre `Eq#`-related things leaking through to GHCi output, even without any special flags enabled. This patch is an attempt to contain some of this strangeness. In particular: * In `TcHsType.etaExpandAlgTyCon`, we propagate through the `AnonArgFlag`s of any `Anon` binders. Previously, we were always hard-coding them to `VisArg`, which meant that invisible binders (like those whose kinds were equality constraint) would mistakenly get flagged as visible. * In `ToIface.toIfaceAppArgsX`, we previously assumed that the argument to a `FunTy` always corresponding to a `Required` argument. We now dispatch on the `FunTy`'s `AnonArgFlag` and map `VisArg` to `Required` and `InvisArg` to `Inferred`. As a consequence, the iface pretty-printer correctly recognizes that equality coercions are inferred arguments, and as a result, only displays them in `-fprint-explicit-kinds` is enabled. * Speaking of iface pretty-printing, `Anon InvisArg` binders were previously being pretty-printed like `T (a :: b ~ c)`, as if they were required. This seemed inconsistent with other invisible arguments (that are printed like `T @{d}`), so I decided to switch this to `T @{a :: b ~ c}`. Along the way, I also cleaned up a minor inaccuracy in the users' guide section for constraints in kinds that was spotted in https://gitlab.haskell.org/ghc/ghc/issues/12102#note_136220. Fixes #12102 and #15872.
* Fix interface version number printing in --show-ifaceÖmer Sinan Ağacan2019-05-031-7/+8
| | | | | | | | | | | | Before Version: Wanted [8, 0, 9, 0, 2, 0, 1, 9, 0, 4, 2, 5], got [8, 0, 9, 0, 2, 0, 1, 9, 0, 4, 2, 5] After Version: Wanted 809020190425, got 809020190425
* Only skip decls with CUSKs with PolyKinds on (fix #16609)Ningning Xie2019-05-033-7/+31
|
* Pattern/expression ambiguity resolutionVladislav Zavialov2019-05-0348-602/+1007
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Hadrian: generate JUnit testsuite report in Linux CI jobAlp Mestanogullari2019-05-031-2/+5
| | | | | | 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.
* testsuite: Mark concprog001 as fragileBen Gamari2019-05-031-0/+1
| | | Due to #16604.
* Make Extension derive BoundedShayne Fletcher2019-05-031-1/+1
|
* Typeset Big-O complexities with Tex-style notation (#16090)Sven Tennie2019-05-032-4/+4
| | | | Use `\min` instead of `min` to typeset it as an operator.
* Emit GHC timing events to eventlogBen Gamari2019-04-301-0/+2
|
* ErrUtils: Emit progress messages to eventlogBen Gamari2019-04-301-3/+5
|
* Build Hadrian with -Werror in the 'ghc-in-ghci' CI jobAlp Mestanogullari2019-04-302-0/+6
|
* Move cGHC_UNLIT_PGM to be "unlit command" in settingsJohn Ericson2019-04-304-8/+5
| | | | | | | | | | | | The bulk of the work was done in #712, making settings be make/Hadrian controlled. This commit then just moves the unlit command rules in make/Hadrian from the `Config.hs` generator to the `settings` generator in each build system. I think this is a good change because the crucial benefit is *settings* don't affect the build: ghc gets one baby step closer to being a regular cabal executable, and make/Hadrian just maintains settings as part of bootstrapping.
* Remove settings.inJohn Ericson2019-04-301-34/+0
| | | | It is no longer needed
* Generate settings by make/hadrian instead of configureJohn Ericson2019-04-3014-21/+257
| | | | This allows it to eventually become stage-specific
* Compute demand signatures assuming idAritySebastian Graf2019-04-3017-174/+505
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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%
* ghci: Ensure that system libffi include path is searchedBen Gamari2019-04-291-0/+2
| | | | Previously hsc2hs failed when building against a system FFI.
* Use pp_itemWojciech Baranowski2019-04-291-3/+1
|
* Suggest only local candidates from global envWojciech Baranowski2019-04-294-8/+11
|
* Comment on 'candidates' functionWojciech Baranowski2019-04-291-0/+2
|
* osa1's patch: consistent suggestion messageWojciech Baranowski2019-04-292-5/+6
|
* Print suggestions in a single messageWojciech Baranowski2019-04-292-7/+9
|