Commit 3dd06d5e authored by Herbert Valerio Riedel's avatar Herbert Valerio Riedel 🕺

Random typo fixes

[skip ci]
parent c5c72aaf
......@@ -192,7 +192,7 @@ where info_ptr and field1..fieldN describe the stack frame, and
arg1..argN are the arguments passed to f using the NativeNodeCall
convention. Note if a field is longer than a word (e.g. a D_ on
a 32-bit machine) then the call will push as many words as
necessary to the stack to accomodate it (e.g. 2).
necessary to the stack to accommodate it (e.g. 2).
----------------------------------------------------------------------------- -}
......
......@@ -440,7 +440,7 @@ ArityType 'at', then
assuming the calls of f respect the one-shot-ness of
its definition.
NB 'f' is an arbitary expression, eg (f = g e1 e2). This 'f'
NB 'f' is an arbitrary expression, eg (f = g e1 e2). This 'f'
can have ArityType as ATop, with length as > 0, only if e1 e2 are
themselves.
......
......@@ -539,7 +539,7 @@ trimConArgs :: AltCon -> [CoreArg] -> [CoreArg]
-- > C b x y -> ...
--
-- We want to drop the leading type argument of the scrutinee
-- leaving the arguments to match agains the pattern
-- leaving the arguments to match against the pattern
trimConArgs DEFAULT args = ASSERT( null args ) []
trimConArgs (LitAlt _) args = ASSERT( null args ) []
......
......@@ -80,7 +80,7 @@ infixl 3 &&&
-}
type IfaceTopBndr = OccName
-- It's convenient to have an OccName in the IfaceSyn, altough in each
-- It's convenient to have an OccName in the IfaceSyn, although in each
-- case the namespace is implied by the context. However, having an
-- OccNames makes things like ifaceDeclImplicitBndrs and ifaceDeclFingerprints
-- very convenient.
......
......@@ -36,7 +36,7 @@ import qualified Data.ByteString.Lazy.Char8 as B8
ELF (Executable and Linking Format) is described in the System V Application
Binary Interface (or ABI). The latter is composed of two parts: a generic
part and a processor specific part. The generic ABI describes the parts of
the interface that remain constant accross all hardware implementations of
the interface that remain constant across all hardware implementations of
System V.
The latest release of the specification of the generic ABI is the version
......
......@@ -132,7 +132,7 @@ acts as a pointer to the value on the heap.
\gram{\ottheap}
Execution procedes until a return value (a literal or a variable, i.e.
pointer to the heap) is produced. To accomodate for let-no-escape
pointer to the heap) is produced. To accommodate for let-no-escape
bindings, we also allow execution to terminate with a jump to a function
application of a let-no-escape variable.
......
......@@ -91,7 +91,7 @@ The above would be rendered as,
Headings
~~~~~~~~
While ReST can accomodate a wide range of heading styles, we have standardized
While ReST can accommodate a wide range of heading styles, we have standardized
on this convention in the User's Guide,
.. code-block:: rest
......
......@@ -115,7 +115,7 @@
How much Haskell stack space to reserve for the saving of registers
etc. in the case of a stack/heap overflow.
This must be large enough to accomodate the largest stack frame
This must be large enough to accommodate the largest stack frame
pushed in one of the heap check fragments in HeapStackCheck.hc
(ie. currently the generic heap checks - 3 words for StgRetDyn,
18 words for the saved registers, see StgMacros.h).
......
......@@ -208,7 +208,7 @@ instance Binary a => Binary (EvalResult a)
--
-- * We print them, e.g. "*** Exception: <something>"
-- * UserInterrupt has a special meaning
-- * In ghc -e, exitWith should exit with the appropraite exit code
-- * In ghc -e, exitWith should exit with the appropriate exit code
--
-- So all we need to do is distinguish UserInterrupt and ExitCode, and
-- all other exceptions can be represented by their 'show' string.
......
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