Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
Open sidebar
Alex D
GHC
Commits
52388421
Commit
52388421
authored
Nov 28, 2016
by
Gabor Greif
💬
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Typos in comments only [ci skip]
parent
6ec2304f
Changes
5
Hide whitespace changes
Inline
Side-by-side
Showing
5 changed files
with
8 additions
and
8 deletions
+8
-8
compiler/main/Plugins.hs
compiler/main/Plugins.hs
+2
-2
compiler/typecheck/TcSMonad.hs
compiler/typecheck/TcSMonad.hs
+1
-1
compiler/types/TyCoRep.hs
compiler/types/TyCoRep.hs
+1
-1
compiler/utils/Digraph.hs
compiler/utils/Digraph.hs
+3
-3
rts/StgCRun.c
rts/StgCRun.c
+1
-1
No files found.
compiler/main/Plugins.hs
View file @
52388421
...
...
@@ -17,7 +17,7 @@ type CommandLineOption = String
-- | 'Plugin' is the core compiler plugin data type. Try to avoid
-- constructing one of these directly, and just modify some fields of
-- 'defaultPlugin' instead: this is to try and preserve source-code
-- compat
a
bility when we add fields to this.
-- compat
i
bility when we add fields to this.
--
-- Nonetheless, this API is preliminary and highly likely to change in
-- the future.
...
...
@@ -32,7 +32,7 @@ data Plugin = Plugin {
-- behaviour of the constraint solver.
}
-- | Default plugin: does nothing at all! For compat
a
bility reasons
-- | Default plugin: does nothing at all! For compat
i
bility reasons
-- you should base all your plugin definitions on this default value.
defaultPlugin
::
Plugin
defaultPlugin
=
Plugin
{
...
...
compiler/typecheck/TcSMonad.hs
View file @
52388421
...
...
@@ -1111,7 +1111,7 @@ But (a) I have been unable to come up with an example of this
(b) see Trac #12660 for how adding the derived shadows
of a Given led to an infinite loop.
(c) It's unlikely that rewriting derived Givens will lead
to a unification becuse Givens don't mention touchable
to a unification bec
a
use Givens don't mention touchable
unification variables
For (b) there may be other ways to solve the loop, but simply
...
...
compiler/types/TyCoRep.hs
View file @
52388421
...
...
@@ -2440,7 +2440,7 @@ pprTyVars tvs = sep (map pprTyVar tvs)
pprTyVar
::
TyVar
->
SDoc
-- Print a type variable binder with its kind (but not if *)
-- Here we do not go via IfaceType, bec
u
ase the duplication with
-- Here we do not go via IfaceType, beca
u
se the duplication with
-- pprIfaceTvBndr is minimal, and the loss of uniques etc in
-- debug printing is disastrous
pprTyVar
tv
...
...
compiler/utils/Digraph.hs
View file @
52388421
...
...
@@ -16,7 +16,7 @@ module Digraph(
findCycle
,
-- For backwards compat
a
bility with the simpler version of Digraph
-- For backwards compat
i
bility with the simpler version of Digraph
stronglyConnCompFromEdgedVerticesOrd
,
stronglyConnCompFromEdgedVerticesOrdR
,
stronglyConnCompFromEdgedVerticesUniq
,
...
...
@@ -286,7 +286,7 @@ decodeSccs Graph { gr_int_graph = graph, gr_vertex_to_node = vertex_fn } forest
mentions_itself
v
=
v
`
elem
`
(
graph
!
v
)
-- The following two versions are provided for backwards compat
a
bility:
-- The following two versions are provided for backwards compat
i
bility:
-- See Note [Deterministic SCC]
-- See Note [reduceNodesIntoVertices implementations]
stronglyConnCompFromEdgedVerticesOrd
...
...
@@ -297,7 +297,7 @@ stronglyConnCompFromEdgedVerticesOrd
=
map
(
fmap
get_node
)
.
stronglyConnCompFromEdgedVerticesOrdR
where
get_node
(
n
,
_
,
_
)
=
n
-- The following two versions are provided for backwards compat
a
bility:
-- The following two versions are provided for backwards compat
i
bility:
-- See Note [Deterministic SCC]
-- See Note [reduceNodesIntoVertices implementations]
stronglyConnCompFromEdgedVerticesUniq
...
...
rts/StgCRun.c
View file @
52388421
...
...
@@ -141,7 +141,7 @@ StgWord8 *win32AllocStack(void)
* we only jump to other STG procedures, so we maintain the 16n - word_size
* alignment for these jumps.
*
* This gives us binary compat
a
bility with LLVM and GCC as well as dealing
* This gives us binary compat
i
bility with LLVM and GCC as well as dealing
* with the FFI. Previously we just maintianed a 16n byte alignment for
* procedure entry and calls, which led to bugs (see #4211 and #5250).
*
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment