From: Ian Lynagh Date: Fri, 27 Feb 2009 02:07:58 +0000 (+0000) Subject: Tweak +RTS --info docs X-Git-Url: http://git.megacz.com/?p=ghc-hetmet.git;a=commitdiff_plain;h=345e841d577eadf30ebca399cc4b8bfd48f9522e Tweak +RTS --info docs --- diff --git a/docs/users_guide/runtime_control.xml b/docs/users_guide/runtime_control.xml index d8735e2..1af2c95 100644 --- a/docs/users_guide/runtime_control.xml +++ b/docs/users_guide/runtime_control.xml @@ -1020,12 +1020,22 @@ char *ghc_rts_opts = "-H128m -K1m"; itself. To do this, use the flag, e.g. $ ./a.out +RTS --info - [("GHC RTS", "Yes") + [("GHC RTS", "YES") ,("GHC version", "6.7") ,("RTS way", "rts_p") ,("Host platform", "x86_64-unknown-linux") + ,("Host architecture", "x86_64") + ,("Host OS", "linux") + ,("Host vendor", "unknown") ,("Build platform", "x86_64-unknown-linux") + ,("Build architecture", "x86_64") + ,("Build OS", "linux") + ,("Build vendor", "unknown") ,("Target platform", "x86_64-unknown-linux") + ,("Target architecture", "x86_64") + ,("Target OS", "linux") + ,("Target vendor", "unknown") + ,("Word size", "64") ,("Compiler unregisterised", "NO") ,("Tables next to code", "YES") ] @@ -1039,8 +1049,8 @@ $ ./a.out +RTS --info GHC RTS - Is this program linked against the GHC RTS? (Currently - the answer is always yes.) + Is this program linked against the GHC RTS? (always + "YES"). @@ -1054,45 +1064,71 @@ $ ./a.out +RTS --info RTS way - The variant (“way”) of the runtime. Possible - values are rts (vanilla), + The variant (“way”) of the runtime. The + most common values are rts (vanilla), rts_thr (threaded runtime, i.e. linked using the -threaded option) and rts_p (profiling runtime, i.e. linked using the -prof - option). Other variants include t - (ticky-ticky profiling) and dyn (the RTS is + option). Other variants include debug + (linked using -debug), + t (ticky-ticky profiling) and + dyn (the RTS is linked in dynamically, i.e. a shared library, rather than statically - linked into the executable itself). + linked into the executable itself). These can be combined, + e.g. you might have rts_thr_debug_p. - Target platform + + Target platform, + Target architecture, + Target OS, + Target vendor + - This is the platform the program is compiled to run on. + These are the platform the program is compiled to run on. - Build platform + + Build platform, + Build architecture, + Build OS, + Build vendor + - This is the platform where the program was compiled - from. (That is, the target platform of GHC itself.) Ordinarily + These are the platform where the program was built + on. (That is, the target platform of GHC itself.) Ordinarily this is identical to the target platform. (It could potentially be different if cross-compiling.) - Host platform + + Host platform, + Host architecture + Host OS + Host vendor + - This is the platform where GHC itself was compiled. + These are the platform where GHC itself was compiled. Again, this would normally be identical to the build and target platforms. + Word size + + Either "32" or "64", + reflecting the word size of the target platform. + + + + Compiler unregistered Was this program compiled with an “unregistered”