From 4df9f0ee56ae232e1cf2f9531205af0dd916b496 Mon Sep 17 00:00:00 2001 From: Orphi Date: Thu, 9 Dec 2010 17:04:40 +0000 Subject: [PATCH] Related to #4826: Some minor tweaks to the wording of the User Guide, section 4.16 --- docs/users_guide/runtime_control.xml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/users_guide/runtime_control.xml b/docs/users_guide/runtime_control.xml index b6cc1ab..22ca59d 100644 --- a/docs/users_guide/runtime_control.xml +++ b/docs/users_guide/runtime_control.xml @@ -10,7 +10,7 @@ code and then links it with a non-trivial runtime system (RTS), which handles storage management, profiling, etc. - If you use the -rtsopts flag when linking, + If you set the -rtsopts flag appropriately when linking, you have some control over the behaviour of the RTS, by giving special command-line arguments to your program. @@ -69,7 +69,8 @@ environment variablefor setting RTS options - When the -rtsopts flag is used when linking, + If the -rtsopts flag is set to + something other than none when linking, RTS options are also taken from the environment variable GHCRTSGHCRTS . For example, to set the maximum heap size @@ -1160,7 +1161,8 @@ The hook ghc_rts_optsghc_rts_opts lets you set RTS - options permanently for a given program. A common use for this is + options permanently for a given program, in the same way as the + newer linker option does. A common use for this is to give your program a default heap and/or stack size that is greater than the default. For example, to set -H128m -K1m, place the following definition in a C source -- 1.7.10.4