X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fphases.xml;h=863838c9772e09bf42cd8964f1dd25a991f25a05;hb=67d845652defc09807eaf134c6d30c8bd26b665a;hp=d1086d8f0ac5cfff1e7ccee19c69b277135d8d3a;hpb=28879d9b3afe1812810d42f14eda6dfa4aa6dc73;p=ghc-hetmet.git diff --git a/docs/users_guide/phases.xml b/docs/users_guide/phases.xml index d1086d8..863838c 100644 --- a/docs/users_guide/phases.xml +++ b/docs/users_guide/phases.xml @@ -5,7 +5,7 @@ Replacing the program for one or more phases phases, changing - + You may specify that a different program be used for one of the phases of the compilation system, in place of whatever the ghc has wired into it. For example, you @@ -71,17 +71,6 @@ - cmd - - - - Use cmd as the - mangler. - - - - - cmd @@ -420,7 +409,7 @@ $ cat foo.hspp for Windows, solaris, etc.). - + arch_HOST_ARCH=1 @@ -448,7 +437,7 @@ $ cat foo.hspp strmod = "\ \ p \ \ " - + don't work with ; /usr/bin/cpp elides the backslash-newline pairs. @@ -463,7 +452,7 @@ $ cat foo.hspp Options affecting a Haskell pre-processor - + pre-processing: custom Pre-processor options @@ -543,21 +532,8 @@ $ cat foo.hspp Use GHC's native code generator rather than - compiling via C. This will compile faster (up to twice as - fast), but may produce code that is slightly slower than - compiling via C. is the default. - - - - - - - - - - Compile via C instead of using the native code - generator. This is the default on architectures for which GHC - doesn't have a native code generator. + compiling via LLVM. + is the default. @@ -569,8 +545,8 @@ $ cat foo.hspp Compile via LLVM instead of using the native code generator. This will generally take slightly longer than the - native code generator to compile but quicker than compiling - via C. Produced code is generally the same speed or faster + native code generator to compile. + Produced code is generally the same speed or faster than the other two code generators. Compiling via LLVM requires LLVM version 2.7 or later to be on the path. @@ -879,11 +855,11 @@ $ cat foo.hspp However, if all the modules are otherwise up to date, you may need to force recompilation both of the module where the new "main" is, and of the module where the "main" function used to be; - ghc is not clever + ghc is not clever enough to figure out that they both need recompiling. You can force recompilation by removing the object file, or by using the flag. - + @@ -952,7 +928,7 @@ $ cat foo.hspp The threaded runtime system provides the following benefits: - + Parallelismparallelism on a multiprocessormultiprocessorSMP or multicoremulticore machine. See . @@ -991,6 +967,86 @@ $ cat foo.hspp + + + + + + This option affects the processing of RTS control options given either + on the command line or via the GHCRTS environment variable. + There are three possibilities: + + + + + + + Disable all processing of RTS options. + If appears anywhere on the command + line, then the program will abort with an error message. + If the GHCRTS environment variable is + set, then the program will emit a warning message, + GHCRTS will be ignored, and the program + will run as normal. + + + + + + + [this is the default setting] Enable + only the "safe" RTS options: (Currently + only + and .) Any other RTS options + on the command line or in the GHCRTS + environment variable causes the program with to abort + with an error message. + + + + + , or + just + + + Enable all RTS option + processing, both on the command line and through + the GHCRTS environment variable. + + + + + + In GHC 6.12.3 and earlier, the default was to process all + RTS options. However, since RTS options can be used to + write logging data to arbitrary files under the security + context of the running program, there is a potential + security problem. For this reason, GHC 7.0.1 and later + default to . + + + + + + + + + + + + This option allows you to set the default RTS options at link-time. For example, + sets the default heap size to 128MB. + This will always be the default heap size for this program, unless the user overrides it. + (Depending on the setting of the option, the user might + not have the ability to change RTS options at run-time, in which case + would be the only way to set + them.) + + + + + + @@ -998,7 +1054,7 @@ $ cat foo.hspp On Windows, GHC normally generates a manifestmanifest - file when linking a binary. The + file when linking a binary. The manifest is placed in the file prog.exe.manifest where prog.exe is the name of the @@ -1018,7 +1074,7 @@ $ cat foo.hspp system using the security control panel, but GHC by default generates binaries that don't depend on the user having disabled installer detection. - + The disables generation of the manifest file. One reason to do this would be if you had a manifest file of your own, for example. @@ -1030,7 +1086,7 @@ $ cat foo.hspp , see below. - + @@ -1046,15 +1102,15 @@ $ cat foo.hspp ; to see exactly what GHC does to embed the manifest, use the flag. A GHC installation comes with its own copy of windres for this reason. - + See also () and + linkend="replacing-phases" />) and (). - + @@ -1069,7 +1125,7 @@ $ cat foo.hspp disk-space cost of creating this import library, which can be substantial - it might require as much space as the code itself, as Haskell DLLs tend to export lots of symbols. - + As long as you are happy to only be able to link to the DLL using GetProcAddress and friends, you can supply the flag to disable the creation of the import