From c8e973ee6d7e3df1ae065cb3a8223a4777a9f4af Mon Sep 17 00:00:00 2001 From: simonmar Date: Wed, 6 Sep 2000 13:11:59 +0000 Subject: [PATCH] [project @ 2000-09-06 13:11:59 by simonmar] Document -unreg and unregisterised compilation. Untested since our DocBook installation is currently broken. --- ghc/docs/users_guide/debugging.sgml | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/ghc/docs/users_guide/debugging.sgml b/ghc/docs/users_guide/debugging.sgml index c143a40..331f7df 100644 --- a/ghc/docs/users_guide/debugging.sgml +++ b/ghc/docs/users_guide/debugging.sgml @@ -701,6 +701,38 @@ file). + + Unregisterised compilation + unregisterised compilation + + The term "unregisterised" really means "compile via vanilla + C", disabling some of the platform-specific tricks that GHC + normally uses to make programs go faster. When compiling + unregisterised, GHC simply generates a C file which is compiled + via gcc. + + Unregisterised compilation can be useful when porting GHC to + a new machine, since it reduces the prerequisite tools to + gcc, as, and + ld and nothing more, and furthermore the amount + of platform-specific code that needs to be written in order to get + unregisterised compilation going is usually fairly small. + + + + : + + + Compile via vanilla ANSI C only, turning off + platform-specific optimisations. NOTE: in order to use + , you need to have a set of libraries + (including the RTS) built for unregisterised compilation. + This amounts to building GHC with way "u" enabled. + + + + +