From: simonpj Date: Wed, 29 Oct 2003 19:05:56 +0000 (+0000) Subject: [project @ 2003-10-29 19:05:55 by simonpj] X-Git-Tag: Approx_11550_changesets_converted~311 X-Git-Url: http://git.megacz.com/?a=commitdiff_plain;h=8c7c30b1221025c0cffb1f14d014078b6e3055fc;p=ghc-hetmet.git [project @ 2003-10-29 19:05:55 by simonpj] Add info about compiling the Main module --- diff --git a/ghc/docs/comm/index.html b/ghc/docs/comm/index.html index bf83fcb..09357b2 100644 --- a/ghc/docs/comm/index.html +++ b/ghc/docs/comm/index.html @@ -74,6 +74,7 @@

GHCi

Compiling and running the Main module

RTS & Libraries

diff --git a/ghc/docs/comm/the-beast/main.html b/ghc/docs/comm/the-beast/main.html new file mode 100644 index 0000000..332ffaa --- /dev/null +++ b/ghc/docs/comm/the-beast/main.html @@ -0,0 +1,35 @@ + + + + + The GHC Commentary - Compiling and running the Main module + + + +

Compiling and running the Main module

+ +GHC allows you to determine which module contains the "main" function, and +what that function is called, via the -fmain-is flag. The trouble is +that the runtime system is fixed, so what symbol should it link to? +

+The current solution is this. Suppose the main function is Foo.run. +

+Then, when compiling module Foo, GHC adds an extra definition: +
```
+  :Main.main = runIO Foo.run
+
```
+Now the RTS can invoke :Main.main to start the program. (This extra +definition is inserted in TcRnDriver.checkMain.) +
+Before starting the program, though, the RTS also initialises the module tree +by calling init_:Main, so when compiling the main module (Foo in this case), +as well as generating init_Foo as usual, GHC also generates +
```
+  init_zcMain() { init_Foo; }
+
```
+This extra initialisation code is generated in CodeGen.mkModuleInit. +

+ + +