Commit 629d01a4 authored by Gabor Greif's avatar Gabor Greif 💬

Typofixes in comments and whitespace only [ci skip]

parent bb50ecaf
......@@ -70,7 +70,7 @@ instance Outputable CmmCat where
-- Why is CmmType stratified? For native code generation,
-- most of the time you just want to know what sort of register
-- to put the thing in, and for this you need to know how
-- many bits thing has and whether it goes in a floating-point
-- many bits thing has, and whether it goes in a floating-point
-- register. By contrast, the distinction between GcPtr and
-- GcNonPtr is of interest to only a few parts of the code generator.
......
......@@ -450,7 +450,7 @@ tidyProgram hsc_env (ModGuts { mg_module = mod
tidyTypeEnv :: Bool -- Compiling without -O, so omit prags
-> TypeEnv -> TypeEnv
-- The competed type environment is gotten from
-- The completed type environment is gotten from
-- a) the types and classes defined here (plus implicit things)
-- b) adding Ids with correct IdInfo, including unfoldings,
-- gotten from the bindings
......@@ -617,7 +617,7 @@ chooseExternalIds hsc_env mod omit_prags expose_all binds implicit_binds imp_id_
-- deterministic, tidy, renaming for all external Ids in this
-- module.
--
-- It is sorted, so that it has adeterministic order (i.e. it's the
-- It is sorted, so that it has a deterministic order (i.e. it's the
-- same list every time this module is compiled), in contrast to the
-- bindings, which are ordered non-deterministically.
init_work_list = zip init_ext_ids init_ext_ids
......
......@@ -267,8 +267,8 @@ pprStatsConflict stats
$$ text "\n")
-- | For every vreg, dump it's how many conflicts it has and its lifetime
-- good for making a scatter plot.
-- | For every vreg, dump how many conflicts it has, and its lifetime.
-- Good for making a scatter plot.
pprStatsLifeConflict
:: [RegAllocStats statics instr]
-> Color.Graph VirtualReg RegClass RealReg -- ^ global register conflict graph
......
......@@ -1420,7 +1420,7 @@ So we compromise, and move their Kind calculation to the call site.
-}
-- | Given the name of the function type constructor and it's kind, create the
-- corresponding 'TyCon'. It is recomended to use 'TyCoRep.funTyCon' if you want
-- corresponding 'TyCon'. It is recommended to use 'TyCoRep.funTyCon' if you want
-- this functionality
mkFunTyCon :: Name -> [TyConBinder] -> Name -> TyCon
mkFunTyCon name binders rep_nm
......
......@@ -473,7 +473,7 @@ addForeignFile = addForeignSource
-- Note that for non-C languages (for example C++) @extern "C"@ directives
-- must be used to get symbols that we can access from Haskell.
--
-- To get better errors, it is reccomended to use #line pragmas when
-- To get better errors, it is recommended to use #line pragmas when
-- emitting C files, e.g.
--
-- > {-# LANGUAGE CPP #-}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment