[GHC] #11735: Optimize coercionKind
GHC
ghc-devs at haskell.org
Sat Jan 27 03:58:20 UTC 2018
#11735: Optimize coercionKind
-------------------------------------+-------------------------------------
Reporter: goldfire | Owner: (none)
Type: task | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 7.10.3
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
Type of failure: Compile-time | Unknown/Multiple
performance bug | Test Case:
Blocked By: | Blocking:
Related Tickets: | Differential Rev(s):
Wiki Page: |
-------------------------------------+-------------------------------------
Comment (by goldfire):
OK. I looked at `pushCoTyArg` and friends, and I have a very simple
solution: just move the `isReflexiveCo` case in `addCoerce` (a local
function within `Simplify.simplCast`) to the top. That should do it. Then
`pushCoTyArg` is never called with a reflexive coercion, and so the
`piResultTy` case won't happen.
Now, `pushCoArgs` might still call `pushCoTyArg` with a reflexive
coercion, but it can be taught not to as well: Have `pushCoArgs` return a
`Maybe ([CoreArg], Maybe Coercion)` and `pushCoArg` return a `Maybe
(CoreArg, Maybe Coercion)`. If the second return values are `Nothing`,
that means that there is no cast (i.e., that the cast would have been
reflexive). The only client of `pushCoArg(s)` is `exprIsConApp_maybe`,
which simply omits a cast if `pushCoArgs` returns `Nothing`. Then, we
never have to bother creating the reflexive coercions.
This should be an easy win all around.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/11735#comment:41>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list