X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fusing.xml;h=60b8f3effc75eefcf6151deda88f78d1dcd6ac6c;hb=949ce3bb4ef2654a814b3549051e439daf82b5e9;hp=c175ca15ffc275591853749fa609f04503d7ca9c;hpb=d39d36f836daa3fecd747ebabde09ac895a9553e;p=ghc-hetmet.git diff --git a/docs/users_guide/using.xml b/docs/users_guide/using.xml index c175ca1..60b8f3e 100644 --- a/docs/users_guide/using.xml +++ b/docs/users_guide/using.xml @@ -842,6 +842,7 @@ ghc -c Foo.hs program. These are: , , + , , , and . The following flags are @@ -931,6 +932,19 @@ ghc -c Foo.hs + : + + + + deprecated-flags + Causes a warning to be emitted when a deprecated + commandline flag is used. + + This option is on by default. + + + + : @@ -982,11 +996,11 @@ ghc -c Foo.hs imported. This happens unless either the Prelude module is explicitly imported with an import ... Prelude ... line, or this implicit import is disabled (either by - or a + or a LANGUAGE NoImplicitPrelude pragma). Note that no warning is given for syntax that implicitly - refers to the Prelude, even if + refers to the Prelude, even if would change whether it refers to the Prelude. For example, no warning is given when 368 means @@ -1522,15 +1536,31 @@ f "2" = 2 - - + + - Turn off the "state hack" whereby any lambda with a - State# token as argument is considered to be - single-entry, hence it is considered OK to inline things inside - it. This can improve performance of IO and ST monad code, but it - runs the risk of reducing sharing. + Turn on call-pattern specialisation. + + + + + + + + + + Turn on the liberate-case transformation. + + + + + + + + + + Turn on the static argument transformation. @@ -1740,7 +1770,7 @@ f "2" = 2 Hints for using SMP parallelism - Add the -sstderr RTS option when + Add the -s RTS option when running the program to see timing stats, which will help to tell you whether your program got faster by using more CPUs or not. If the user time is greater than @@ -1806,16 +1836,15 @@ statements or clauses. intermediate code generation GHC can dump its optimized intermediate code (said to be in “Core” format) - to a file as a side-effect of compilation. Core files, which are given the suffix - .hcr, can be read and processed by non-GHC back-end - tools. The Core format is formally described in + to a file as a side-effect of compilation. Non-GHC back-end tools can read and process Core files; these files have the suffix + .hcr. The Core format is described in An External Representation for the GHC Core Language, - and sample tools (in Haskell) - for manipulating Core files are available in the GHC source distribution - directory /fptools/ghc/utils/ext-core. + and sample tools + for manipulating Core files (in Haskell) are in the GHC source distribution + directory under utils/ext-core. Note that the format of .hcr - files is different (though similar) to the Core output format generated - for debugging purposes (). + files is different from the Core output format that GHC generates + for debugging purposes (), though the two formats appear somewhat similar. The Core format natively supports notes which you can add to your source code using the CORE pragma (see -GHC can also read in External Core files as source; just give the .hcr file on -the command line, instead of the .hs or .lhs Haskell source. -A current infelicity is that you need to give the -fglasgow-exts flag too, because -ordinary Haskell 98, when translated to External Core, uses things like rank-2 types. +Currently (as of version 6.8.2), GHC does not have the ability to read in External Core files as source. If you would like GHC to have this ability, please make your wishes known to the GHC Team. + &debug;