- 07 Jun, 2022 1 commit
-
-
Alexis King authored
wip: first stab at RESET frames, continuation capturing wip: first stab at applyContinuation wip: fix some oversights/typos wip: fix some bugs wip: move continuation C code into separate file wip: eliminate separate RESET_FRAME closure type wip: fix info table comparison check wip: remove a few lingering bits wip: fix strictness signature on shift# wip: change shift# to compose two continuations wip: fix calling conventions in Cmm code wip: make continuations levity-polymorphic wip: copy the stack frames on continuation restore if they fit wip: add missing RTS symbols wip: give .c and .cmm files different names wip: move Cmm definition before use wip: rewrite continuation support to use separate StgContinuation wip: misc fixes wip: change calling conventions around continuation restore wip: allow the top of the continuation to be levity-polymorphic wip: Make shift# lazy in its first argument This is necessary for a similar reason to why it’s necessary for catch#. wip: Rename reset#/shift# to prompt#/control0# wip: add PromptTag# type and newPromptTag# primop wip: add PROMPT_FRAME closure type, make control0# use prompt tags wip: add MASK_FRAME and restructure exceptions code to use it wip: basic async exception support for continuations wip: raise an error when no matching continuation prompt is found wip: remove unneeded closure types, add lots of comments wip: fix TraverseHeap.c wip: represent prompt tags as unlifted closures, not Word64s wip: reinstate cancellative behavior of mask/unmask operations wip: remove stg_keepMaskingState_ret wip: give apply_mask_frame a more specific type wip: include the types of prompt#/control0# in the introductory Note wip: fix typo wip: reference the incompatibility with thunk updates earlier wip: add Note [Detecting illegal captures is not guaranteed] wip: add some comments to clarify captureContinuationAndAbort wip: eliminate unneeded `unwind` annotation wip: fix rts/Printer.c wip: Remove unhelpful comment about “special layout” wip: add signatures in comments wip: fix polymorphism in the type of control0# wip: make PromptTag# levity-monomorphic wip: add docs for continuation primops
-
- 06 Jun, 2022 3 commits
-
-
-
Replaces uses of `TcRnUnknownMessage` with proper diagnostics constructors in `GHC.Tc.Gen.Match`, `GHC.Tc.Gen.Pat`, and `GHC.Tc.Gen.Sig`.
-
This commit fixes #20312 It deprecates "TypeInType" extension according to the following proposal: https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0083-no-type-in-type.rst It has been already implemented. The migration strategy: 1. Disable TypeInType 2. Enable both DataKinds and PolyKinds extensions Metric Decrease: T16875
-
- 02 Jun, 2022 10 commits
-
-
John Ericson authored
Finishes what !7467 (closed) started. Progress towards #17957
-
We have the length already, so we might as well use that rather than O(n) recomputing it.
-
John Ericson authored
As proposed in ghc/ghc!7508 (comment 432877) and ghc/ghc!7508 (comment 434676), `GHC.HsToCore.Ticks` is about ticks, breakpoints are separate and backend-specific (only for the bytecode interpreter), and mix entry writing is just for HPC. With this split we separate out those interpreter- and HPC-specific its, and keep the main `GHC.HsToCore.Ticks` agnostic. Also, instead of passing the reversed list and count around, we use `SizedSeq` which abstracts over the algorithm. This is much nicer to avoid noise and prevents bugs. (The bugs are not just hypothetical! I missed up the reverses on an earlier draft of this commit.)
-
John Ericson authored
The old name made it confusing why disabling HPC didn't disable the entire pass. The name makes it clear --- there are other reasons to add ticks in addition.
-
John Ericson authored
No need to inline traversing a maybe for `mkModBreaks`. And better to make each function do one thing and let the caller deside when than scatter the decision making and make the caller seem more imperative.
-
John Ericson authored
-
-
-
This is a follow-up to !7247 (closed) making the inclusion of compact unwinding sections the default. Also a slight refactoring/simplification of the flag handling to add -fno-compact-unwind.
-
This allows us to see the output of hadrian while it is doing the setup.
-
- 01 Jun, 2022 11 commits
-
-
To current `master`. (cherry picked from commit fbb59c21)
-
Metric Decrease: T5631 Metric Increase: T18223 (cherry picked from commit 55fcee30) -
Fixes #21675.
-
-
-
-
Switch to a pure Haskell implementation of base:GHC.Unicode, based on the implementation of the package unicode-data (https://github.com/composewell/unicode-data/). Approved by CLC as per https://github.com/haskell/core-libraries-committee/issues/59#issuecomment-1132106691. - Remove current Unicode cbits. - Add generator for Unicode property files from Unicode Character Database. - Generate internal modules. - Update GHC.Unicode. - Add unicode003 test for general categories and case mappings. - Add Python scripts to check 'base' Unicode tests outputs and characters properties. Fixes #21375 ------------------------- Metric Decrease: T16875 Metric Increase: T4029 T18304 haddock.base -------------------------
-
Fixes #21619
-
This commit redefines the structure of Splices in the AST. We get rid of `HsSplice` which used to represent typed and untyped splices, quasi quotes, and the result of splicing either an expression, a type or a pattern. Instead we have `HsUntypedSplice` which models an untyped splice or a quasi quoter, which works in practice just like untyped splices. The `HsExpr` constructor `HsSpliceE` which used to be constructed with an `HsSplice` is split into `HsTypedSplice` and `HsUntypedSplice`. The former is directly constructed with an `HsExpr` and the latter now takes an `HsUntypedSplice`. Both `HsType` and `Pat` constructors `HsSpliceTy` and `SplicePat` now take an `HsUntypedSplice` instead of a `HsSplice` (remember only /untyped splices/ can be spliced as types or patterns). The result of splicing an expression, type, or pattern is now comfortably stored in the extension fields `XSpliceTy`, `XSplicePat`, `XUntypedSplice` as, respectively, `HsUntypedSpliceResult (HsType Ghc...
-
UntypedSpliceFlavour was only used in the client-specific `GHC.Hs.Expr` but was defined in the client-independent L.H.S.Expr.
-
-
- 31 May, 2022 4 commits
-
-
John Ericson authored
Progress towards #17957 Because of `CoreM`, I did not move the `DynFlags` and `HscEnv` to other modules as thoroughly as I usually do. This does mean that risk of `DynFlags` "creeping back in" is higher than it usually is. After we do the same process to the other Core passes, and then figure out what we want to do about `CoreM`, we can finish the job started here. That is a good deal more work, however, so it certainly makes sense to land this now.
-
-
This helps tracing errors which happen when building stage1
-
These executables (such as hsc2hs) are built using the boot compiler and crucially, most libraries from the global package database. We also move other build-time executables to be built in this stage such as linters which also cleans up which libraries end up in the global package database. This allows us to remove hacks where linters-common is removed from the package database when a bindist is created. This fixes issues caused by infinite recursion due to bytestring adding a dependency on template-haskell. Fixes #21634
-
- 30 May, 2022 11 commits
-
-
-
-
Now #21563 is fixed we can properly enable `-dlint` in CI rather than a subset of the flags.
-
We originally planned to remove the flag in 9.4 but there's actually no great rush to do so and it's probably less confusing (forever) to keep the message around suggesting an explicit profiling option. Fixes #21545
-
-
-
-
This fixes two bugs which were adding dependencies on alex/happy when building from a source dist. * When we try to pass `--with-alex` and `--with-happy` to cabal when configuring but the builders are not set. This is fixed by making them optional. * When we configure, cabal requires alex/happy because of the build-tool-depends fields. These are now made optional with a cabal flag (build-tool-depends) for compiler/hpc-bin/genprimopcode. Fixes #21627
-
This is a large collection of changes all relating to eta reduction, originally triggered by #18993, but there followed a long saga. Specifics: * Move state-hack stuff from GHC.Types.Id (where it never belonged) to GHC.Core.Opt.Arity (which seems much more appropriate). * Add a crucial mkCast in the Cast case of GHC.Core.Opt.Arity.eta_expand; helps with T18223 * Add clarifying notes about eta-reducing to PAPs. See Note [Do not eta reduce PAPs] * I moved tryEtaReduce from GHC.Core.Utils to GHC.Core.Opt.Arity, where it properly belongs. See Note [Eta reduce PAPs] * In GHC.Core.Opt.Simplify.Utils.tryEtaExpandRhs, pull out the code for when eta-expansion is wanted, to make wantEtaExpansion, and all that same function in GHC.Core.Opt.Simplify.simplStableUnfolding. It was previously inconsistent, but it's doing the same thing. * I did a substantial refactor of ArityType; see Note [ArityType]. This allowed me to do away with the somewhat myster...
-
This patch concerns #20155, part (1) The general idea is that since primops have curried bindings (currently in PrimOpWrappers.hs) we don't need to eta-expand them. But we /do/ need to eta-expand the levity-polymorphic ones, because they /don't/ have bindings. This patch makes a start in that direction, by identifying the levity-polymophic primops in the PrimOpId IdDetails constructor. For the moment, I'm still eta-expanding all primops (by saying that hasNoBinding returns True for all primops), because of the bug reported in #20155. But I hope that before long we can tidy that up too, and remove the TEMPORARILY stuff in hasNoBinding.
-
-
