diff options
Diffstat (limited to 'compiler/GHC/Driver')
| -rw-r--r-- | compiler/GHC/Driver/Backend.hs | 2 | ||||
| -rw-r--r-- | compiler/GHC/Driver/Make.hs | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/compiler/GHC/Driver/Backend.hs b/compiler/GHC/Driver/Backend.hs index afe8176f78..48958594fd 100644 --- a/compiler/GHC/Driver/Backend.hs +++ b/compiler/GHC/Driver/Backend.hs @@ -27,7 +27,7 @@ especially the driver. Examples include the following: this back end, then these are the command-line flags you should add to any invocation of the C compiler." -These properties are use elsewhere in GHC, primarily in the driver, to +These properties are used elsewhere in GHC, primarily in the driver, to fine-tune operations according to the capabilities of the chosen back end. You might use a property to make GHC aware of a potential limitation of certain back ends, or a special feature available only diff --git a/compiler/GHC/Driver/Make.hs b/compiler/GHC/Driver/Make.hs index cb0efac6ad..09e6be023a 100644 --- a/compiler/GHC/Driver/Make.hs +++ b/compiler/GHC/Driver/Make.hs @@ -2632,7 +2632,7 @@ X.hs module X where data XT = MkX T fx = ...g... ``` -If in `--make` we compile R.hs-boot, then A.hs, then X.hs, we'll get a `ModDetails` for `X` that has an AbstractTyCon for `T` in the the argument type of `MkX`. So: +If in `--make` we compile R.hs-boot, then A.hs, then X.hs, we'll get a `ModDetails` for `X` that has an AbstractTyCon for `T` in the argument type of `MkX`. So: * Either we should delay compiling X until after R has been compiled. (This is what we do) * Or we should rehydrate X after compiling R -- because it transitively depends on R.hs-boot. |