Commit 306fce60 authored by Gabor Greif's avatar Gabor Greif 💬

Strings and comments only: 'to to ' fixes

I'd still prefer if a native english speaker would check them.
parent 0717462d
......@@ -79,7 +79,7 @@ Things to do:
into separate C procedures.
Short term:
compute and attach liveness into to LastCall
compute and attach liveness into LastCall
right at end, split, cvt to old rep
[must split before cvt, because old rep is not expressive enough]
......
......@@ -86,7 +86,7 @@ data BCInstr
-- designers of the new Foreign library. In particular it is
-- quite impossible to convert an Addr to any other integral
-- type, and it appears impossible to get hold of the bits of
-- an addr, even though we need to to assemble BCOs.
-- an addr, even though we need to assemble BCOs.
-- various kinds of application
| PUSH_APPLY_N
......
......@@ -780,7 +780,7 @@ lookupImpDeprec iface gre
Note [Used names with interface not loaded]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It's (just) possible to to find a used
It's (just) possible to find a used
Name whose interface hasn't been loaded:
a) It might be a WiredInName; in that case we may not load
......
......@@ -722,7 +722,7 @@ See Note [Loop breaking and RULES] in OccAnal.
\begin{code}
addBndrRules :: SimplEnv -> InBndr -> OutBndr -> (SimplEnv, OutBndr)
-- Rules are added back in to to the bin
-- Rules are added back into the bin
addBndrRules env in_id out_id
| isEmptySpecInfo old_rules = (env, out_id)
| otherwise = (modifyInScope env final_id, final_id)
......
......@@ -691,7 +691,7 @@ pprTcApp p pp tc tys
pprTypeApp :: TyCon -> [Type] -> SDoc
pprTypeApp tc tys
= ppr_type_name_app TopPrec ppr_type (getName tc) (ppr tc) tys
-- We have to to use ppr on the TyCon (not its name)
-- We have to use ppr on the TyCon (not its name)
-- so that we get promotion quotes in the right place
pprTypeNameApp :: Prec -> (Prec -> a -> SDoc) -> Name -> [a] -> SDoc
......
......@@ -194,7 +194,7 @@ indexBuiltin fn f i bi
text "' is not yet implemented."
, text "This function does not appear in your source program, but it is needed"
, text "to compile your code in the backend. This is a known, current limitation"
, text "of DPH. If you want it to to work you should send mail to cvs-ghc@haskell.org"
, text "of DPH. If you want it to work, you should send mail to cvs-ghc@haskell.org"
, text "and ask what you can do to help (it might involve some GHC hacking)."])
where xs = f bi
......@@ -213,5 +213,5 @@ lookupEnvBuiltin fn env n
text "' is not yet implemented."
, text "This function does not appear in your source program, but it is needed"
, text "to compile your code in the backend. This is a known, current limitation"
, text "of DPH. If you want it to to work you should send mail to cvs-ghc@haskell.org"
, text "of DPH. If you want it to work, you should send mail to cvs-ghc@haskell.org"
, text "and ask what you can do to help (it might involve some GHC hacking)."])
......@@ -255,7 +255,7 @@ of certain types of closures and their layout.
When building the runtime system, the @gcc@ compiler correctly figures out
the size of every structure on its own.
However,
GHC simply reads @includes/Constants.h@ to to determine the size of
GHC simply reads @includes/Constants.h@ to determine the size of
closures assumed by the runtime system.
Thus, we must change the constants used by the GHC itself (as opposed to
the runtime system). They are all found in @includes/Constants.h@.
......
......@@ -3753,7 +3753,7 @@ ocGetNames_PEi386 ( ObjectCode* oc )
* => I suspect we've been incorrectly handling .bss sections in (relocatable)
* object files up until now. This turned out to bite us with ghc-6.4.1's use
* of gcc-3.4.x, which has started to emit initially-zeroed-out local 'static'
* variable decls into to the .bss section. (The specific function in Q which
* variable decls into the .bss section. (The specific function in Q which
* triggered this is libraries/base/cbits/dirUtils.c:__hscore_getFolderPath())
*/
if (sectab_i->VirtualSize == 0 && sectab_i->SizeOfRawData == 0) continue;
......
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