X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fseparate_compilation.xml;h=9ce971d511ca5c9c4c3ade957f3a58ddefac950a;hb=163d12852002a67c5b661b4b3e7e3c5bb6faa5f3;hp=91cefb449c339a5a1bb7a77fc9247f4193cf2ba8;hpb=4813940fdda66861c686e8fd0527c6c5d0b69b1d;p=ghc-hetmet.git
diff --git a/docs/users_guide/separate_compilation.xml b/docs/users_guide/separate_compilation.xml
index 91cefb4..9ce971d 100644
--- a/docs/users_guide/separate_compilation.xml
+++ b/docs/users_guide/separate_compilation.xml
@@ -184,7 +184,7 @@
dots replaced by the directory separator ('/' or '\', depending
on the system), and extension is a
source extension (hs, lhs)
- if we are in mode and GHCi, or
+ if we are in mode or GHCi, or
hisuf otherwise.
For example, suppose the search path contains directories
@@ -220,7 +220,7 @@
This isn't the whole story: GHC also looks for modules in
pre-compiled libraries, known as packages. See the section on
- packages (), for details.
+ packages () for details.
@@ -299,7 +299,7 @@
dir. For example:
-$ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `arch`
+$ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `uname -m`
The object files, Foo.o,
@@ -374,6 +374,20 @@ $ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `arch`
+
+
+ dir
+
+
+
+ The option is shorthand for
+ the combination
+ of , ,
+ and .
+
+
+
+
suffix
@@ -426,6 +440,8 @@ $ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `arch`
.hc files, saving
+ .ll files, saving
+ .s files, saving
@@ -436,7 +452,9 @@ $ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `arch`
+ ,
+
@@ -451,7 +469,26 @@ $ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `arch`
+ ,
+
+
+
+
+
+ Keep intermediate .ll files when
+ doing .hs-to-.o
+ compilations via LLVM (NOTE: .ll files
+ aren't generated when using the native code generator, you
+ may need to use to force them
+ to be produced).
+
+
+
+
+
+ ,
+
@@ -461,7 +498,9 @@ $ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `arch`
+ ,
+
@@ -559,9 +598,9 @@ $ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `arch`
the same as the old one; this is friendly to
make. When an interface does change,
it is often enlightening to be informed. The
- option will make GHC run
- diff on the old and new
- .hi files.
+ option will make GHC
+ report the differences between the old and
+ new .hi files.
@@ -589,9 +628,9 @@ $ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `arch`
- Where file is the name of
+ where file is the name of
an interface file, dumps the contents of that interface in
- a human-readable (ish) format.
+ a human-readable (ish) format. See .
@@ -641,24 +680,24 @@ $ ghc -c parse/Foo.hs parse/Bar.hs gurgle/Bumble.hs -odir `arch`
B, say) may conceivably not change
B.hi one jot. So now…
- GHC keeps a version number on each interface file, and on
- each type signature within the interface file. It also keeps in
- every interface file a list of the version numbers of everything
- it used when it last compiled the file. If the source file's
- modification date is earlier than the .o
- file's date (i.e. the source hasn't changed since the file was
- last compiled), and the recompilation checking is on, GHC will be
- clever. It compares the version numbers on the things it needs
- this time with the version numbers on the things it needed last
- time (gleaned from the interface file of the module being
- compiled); if they are all the same it stops compiling rather
- early in the process saying “Compilation IS NOT
- required”. What a beautiful sight!
-
- Patrick Sansom had a workshop paper about how all this is
- done (though the details have changed quite a bit). Ask him if you want a
- copy.
+ GHC calculates a fingerprint (in fact an MD5 hash) of each
+ interface file, and of each declaration within the interface
+ file. It also keeps in every interface file a list of the
+ fingerprints of everything it used when it last compiled the
+ file. If the source file's modification date is earlier than
+ the .o file's date (i.e. the source hasn't
+ changed since the file was last compiled), and the recompilation
+ checking is on, GHC will be clever. It compares the fingerprints
+ on the things it needs this time with the fingerprints
+ on the things it needed last time (gleaned from the
+ interface file of the module being compiled); if they are all
+ the same it stops compiling early in the process saying
+ “Compilation IS NOT required”. What a beautiful
+ sight!
+
+ You can read
+ about how
+ all this works in the GHC commentary.
@@ -696,8 +735,11 @@ module B where
hi-boot files
Here A imports B, but B imports
A with a {-# SOURCE #-} pragma, which breaks the
-circular dependency. For every module A.hs that is {-# SOURCE #-}-imported
-in this way there must exist a souce file A.hs-boot. This file contains an abbreviated
+circular dependency. Every loop in the module import graph must be broken by a {-# SOURCE #-} import;
+or, equivalently, the module import graph must be acyclic if {-# SOURCE #-} imports are ignored.
+
+For every module A.hs that is {-# SOURCE #-}-imported
+in this way there must exist a source file A.hs-boot. This file contains an abbreviated
version of A.hs, thus:
module A where
@@ -706,7 +748,7 @@ module A where
To compile these three files, issue the following commands:
- ghc -c A.hs-boot -- Poduces A.hi-boot, A.o-boot
+ ghc -c A.hs-boot -- Produces A.hi-boot, A.o-boot
ghc -c B.hs -- Consumes A.hi-boot, produces B.hi, B.o
ghc -c A.hs -- Consumes B.hi, produces A.hi, A.o
ghc -o foo A.o B.o -- Linking the program
@@ -772,7 +814,7 @@ When a hs-boot file A.hs-boot A module M that is
{-# SOURCE #-}-imported in a program will usually also be
ordinarily imported elsewhere. If not, ghc --make
- automatically adds M to the set of moudles it tries to
+ automatically adds M to the set of modules it tries to
compile and link, to ensure that M's implementation is included in
the final program.
@@ -818,7 +860,7 @@ can be given abstractly, by omitting the '=' sign and everything that follows.
data R (x :: * -> *) y
-You cannot use deriving on a data type declaration; write in
+You cannot use deriving on a data type declaration; write an
instance declaration instead.
Class declarations is exactly as in Haskell, except that you may not put
@@ -1002,15 +1044,7 @@ M.o : X.hi-boot
option below).The dependency generation phase of GHC can take some
- additional options, which you may find useful. For historical
- reasons, each option passed to the dependency generator from
- the GHC command line must be preceded by
- -optdep. For example, to pass -f
- .depend to the dependency generator, you say
-
-
-ghc -M -optdep-f -optdep.depend ...
-
+ additional options, which you may find useful.
The options which affect dependency generation are:
@@ -1019,22 +1053,14 @@ ghc -M -optdep-f -optdep.depend ...
Display a list of the cycles in the module graph. This is
- useful when trying to eliminate such cycles. You do not need the -optdep prefix
- for this flag.
-
-
-
-
-
-
- Turn off warnings about interface file shadowing.
+ useful when trying to eliminate such cycles.
- Print a full list of the module depenencies to stdout.
+ Print a full list of the module dependencies to stdout.
(This is the standard verbosity flag, so the list will
also be displayed with and
;
@@ -1043,14 +1069,14 @@ ghc -M -optdep-f -optdep.depend ...
- file
+ fileUse file as the makefile,
rather than makefile or
Makefile. If
file doesn't exist,
mkdependHS creates it. We often use
- to put the dependencies in
+ to put the dependencies in
.depend and then
include the file
.depend into
@@ -1058,21 +1084,8 @@ ghc -M -optdep-f -optdep.depend ...
-
-
-
+ Make extra dependencies that declare that files
with suffix
@@ -1081,13 +1094,14 @@ ghc -M -optdep-f -optdep.depend ...
.<suf>_hi, or (for
{-# SOURCE #-}
imports) on .hi-boot. Multiple
- flags are permitted. For example,
- will make dependencies
- for .hc on
+ flags are permitted. For example,
+
+ will make dependencies
+ for .hs on
.hi,
- .a_hc on
+ .a_hs on
.a_hi, and
- .b_hc on
+ .b_hs on
.b_hi. (Useful in
conjunction with NoFib "ways".)
@@ -1103,35 +1117,6 @@ ghc -M -optdep-f -optdep.depend ...
-
-
- same as
-
-
-
-
-
- Regard modules imported from packages as unstable,
@@ -1160,7 +1145,8 @@ just in case they contain an instance declaration that matters to M. This would
be a disaster in practice, so GHC tries to be clever. In particular, if an instance declaration is in the same module as the definition
-of any type or class mentioned in the head of the instance declaration, then
+of any type or class mentioned in the head of the instance declaration
+(the part after the “=>”; see ), then
GHC has to visit that interface file anyway. Example:
module A where
@@ -1178,8 +1164,31 @@ and GHC has no other reason for visiting the module. Example:
class C a where ...
Here, neither D nor T is declared in module Orphan.
-We call such modules ``orphan modules'',
-defined thus:
+We call such modules “orphan modules”.
+GHC identifies orphan modules, and visits the interface file of
+every orphan module below the module being compiled. This is usually
+wasted work, but there is no avoiding it. You should therefore do
+your best to have as few orphan modules as possible.
+
+
+Functional dependencies complicate matters. Suppose we have:
+
+ module B where
+ instance E T Int where ...
+ data T = ...
+
+Is this an orphan module? Apparently not, because T
+is declared in the same module. But suppose class E had a
+functional dependency:
+
+ module Lib where
+ class E x y | y -> x where ...
+
+Then in some importing module M, the constraint (E a Int) should be "improved" by setting
+a = T, even though there is no explicit mention
+of T in M.
+
+These considerations lead to the following definition of an orphan module:
An orphan moduleorphan module
@@ -1187,12 +1196,21 @@ defined thus:
least one orphan rule. An instance declaration in a module M is an orphan instance if
- orphan instance
- none of the type constructors
- or classes mentioned in the instance head (the part after the ``=>'') are declared
- in M.
-
- Only the instance head counts. In the example above, it is not good enough for C's declaration
+ orphan instance
+
+
+ The class of the instance declaration is not declared in M, and
+
+
+Either the class has no functional dependencies, and none of the type constructors
+ in the instance head is declared in M; or there
+ is a functional dependency for which none of the type constructors mentioned
+ in the non-determined part of the instance head is defined in M.
+
+
+
+ Only the instance head
+ counts. In the example above, it is not good enough for C's declaration
to be in module A; it must be the declaration of D or T.
@@ -1204,17 +1222,18 @@ defined thus:
- GHC identifies orphan modules, and visits the interface file of
-every orphan module below the module being compiled. This is usually
-wasted work, but there is no avoiding it. You should therefore do
-your best to have as few orphan modules as possible.
+If you use the flag , GHC will warn you
+if you are creating an orphan module.
+Like any warning, you can switch the warning off with ,
+and
+will make the compilation fail if the warning is issued.
-
- You can identify an orphan module by looking in its interface
+
+You can identify an orphan module by looking in its interface
file, M.hi, using the
-. If there is a ``!'' on the first line,
-GHC considers it an orphan module.
+ mode. If there is a [orphan module] on the
+first line, GHC considers it an orphan module.
@@ -1222,7 +1241,6 @@ GHC considers it an orphan module.