X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fusing.xml;h=21e5205022150da4510fe55f7e1cebd245941906;hb=9d03becc597e5b1ab6c8466209a1263bf8ba6f29;hp=5d92ab2a24b5617371f356a515c1eb5b38bd5a1f;hpb=5263c9ab4408e3b62dbf7505ab40a81946d4e49b;p=ghc-hetmet.git diff --git a/docs/users_guide/using.xml b/docs/users_guide/using.xml index 5d92ab2..21e5205 100644 --- a/docs/users_guide/using.xml +++ b/docs/users_guide/using.xml @@ -342,6 +342,20 @@ module X where + ghc --show-iface file + + + + + Read the interface in + file and dump it as text to + stdout. For example ghc --show-iface M.hi. + + + + + + ghc --supported-languages @@ -408,20 +422,6 @@ module X where - - - - ghc --print-docdir - - - - - Print the path to GHC's documentation directory. Note that - some distributions do no include the documentation, in which case - this directory may be empty or may not exist. - - - @@ -1522,15 +1522,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. @@ -1602,24 +1618,6 @@ f "2" = 2 - - - - - Switches on an experimental "optimisation". - Switching it on makes the compiler a little keener to - inline a function that returns a constructor, if the - context is that of a thunk. - - x = plusInt a b - - If we inlined plusInt we might get an opportunity to use - update-in-place for the thunk 'x'. - - - - - : inlining, controlling @@ -1824,16 +1822,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;