summaryrefslogtreecommitdiff
path: root/compiler/cmm
diff options
context:
space:
mode:
authorGabor Greif <ggreif@gmail.com>2018-06-26 15:29:14 +0200
committerGabor Greif <ggreif@gmail.com>2018-06-26 15:29:14 +0200
commit629d01a436d8041d44ed2826eb3f75e3f2d9ab47 (patch)
treeaf3f94eece0c57728aa9c50100df8b5e746d6998 /compiler/cmm
parentbb50ecaf2930455a6ecb7268f9c0f2ee909f5361 (diff)
downloadhaskell-629d01a436d8041d44ed2826eb3f75e3f2d9ab47.tar.gz
Typofixes in comments and whitespace only [ci skip]
Diffstat (limited to 'compiler/cmm')
-rw-r--r--compiler/cmm/CmmType.hs2
1 files changed, 1 insertions, 1 deletions
diff --git a/compiler/cmm/CmmType.hs b/compiler/cmm/CmmType.hs
index 0538b9fea3..97b181a243 100644
--- a/compiler/cmm/CmmType.hs
+++ b/compiler/cmm/CmmType.hs
@@ -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.