From 465d1c07cc5afd809bba071b0c1b54cb8ea8e102 Mon Sep 17 00:00:00 2001 From: sof Date: Fri, 25 Jul 1997 22:39:14 +0000 Subject: [PATCH] [project @ 1997-07-25 22:39:14 by sof] Doc updates --- ghc/docs/users_guide/how_to_run.lit | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/ghc/docs/users_guide/how_to_run.lit b/ghc/docs/users_guide/how_to_run.lit index 87e016c..52617ef 100644 --- a/ghc/docs/users_guide/how_to_run.lit +++ b/ghc/docs/users_guide/how_to_run.lit @@ -208,11 +208,14 @@ better code than \tr{-O}. \item[\tr{-fvia-C}:] \index{-fvia-C option} +\index{-fvia-c option} Compile via C, and don't use the native-code generator. (There are many cases when GHC does this on its own.) You might pick up a little bit of speed by compiling via C. If you use \tr{_ccall_}s or \tr{_casm_}s, you probably {\em have to} use -\tr{-fvia-C}. +\tr{-fvia-C}. + +The lower-case incantation, \tr{-fvia-c}, is synonymous. \item[\tr{-O2-for-C}:] \index{-O2-for-C option} @@ -488,7 +491,9 @@ The compiler does not overwrite an existing \tr{.hi} interface file if the new one is byte-for-byte the same as the old one; this is friendly to \tr{make}. When an interface does change, it is often enlightening to be informed. The \tr{-hi-diffs}\index{-hi-diffs option} option will -make \tr{ghc} run \tr{diff} on the old and new \tr{.hi} files. +make \tr{ghc} run \tr{diff} on the old and new \tr{.hi} files. You can +also record the difference in the interface file itself, the +\tr{-keep-hi-diffs}\index{-keep-hi-diffs} option takes care of that. The \tr{.hi} files from GHC 2.xx contain ``usage'' information which changes often and uninterestingly. If you really want to see these @@ -1239,7 +1244,7 @@ trademark of Peyton Jones Enterprises, plc.) \index{source-file options} Sometimes it is useful to make the connection between a source file -and the command-line options it requires, quite tight. For instance, +and the command-line options it requires quite tight. For instance, if a (Glasgow) Haskell source file uses \tr{casm}s, the C back-end often needs to be told about which header files to include. Rather than maintaining the list of files the source depends on in a @@ -1262,6 +1267,10 @@ are just included literally in the array of command-line arguments the compiler driver maintains internally, so you'll be desperately disappointed if you try to glob etc. inside \tr{OPTIONS}. +NOTE: the contents of OPTIONS are prepended to the command-line +options, so you *do* have the ability to override OPTIONS settings +via the command line. + It is not recommended to move all the contents of your Makefiles into your source files, but in some circumstances, the \tr{OPTIONS} pragma is the Right Thing. (If you use \tr{-keep-hc-file-too} and have OPTION -- 1.7.10.4