[Git][ghc/ghc][wip/21611-move-corem] Applied suggestion: Description of Core Optimizer stages

[Dominik Peteler (@mmhat)]

Dominik Peteler pushed to branch wip/21611-move-corem at Glasgow Haskell Compiler / GHC


Commits:
a3e5360a by John Ericson at 2022-09-27T20:42:52+00:00
Applied suggestion: Description of Core Optimizer stages
- - - - -


1 changed file:

- compiler/GHC/Driver/Core/Opt.hs


Changes:

=====================================
compiler/GHC/Driver/Core/Opt.hs
=====================================
@@ -129,8 +129,8 @@ Note [The architecture of the Core optimizer]
 
 Conceptually the Core optimizer consists of two stages:
 
- 1. The planning stage.
- 2. The execution stage.
+ 1. **The planning stage**: where we take the user-specified input (currently in `DynFlags`) and produce a domain-specific configuration for just this pipeline stage (a `[CoreToDo]` value). This configuration is the plan.
+ 2. **The execution stage**: where we we take a Core program (a `ModGuts`) and the configuration (a `[CoreToDo]`) and optimize that program according to the `[CoreToDo]` plan, producing a new `ModGuts`.
 
 This division is mirrored in the interface of the different optimizations. For
 each of those optimzations we have



View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/commit/a3e5360a3b9d45e1a9a0db0ba8dd1d1c902399b3

-- 
View it on GitLab: https://gitlab.haskell.org/ghc/ghc/-/commit/a3e5360a3b9d45e1a9a0db0ba8dd1d1c902399b3
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/20220927/3965c61e/attachment.html>