From ded67816a2baf995081d1772aa7d83c7e51a284b Mon Sep 17 00:00:00 2001 From: Simon Marlow Date: Thu, 26 Jul 2007 09:40:30 +0000 Subject: [PATCH 1/1] Documentation updates for #1177 We now have a section that describes what hs_exit() does (including the "wait for foreign calls to return" behaviour), and more documentation on creating libraries of Haskell code. I also imported the section "Beware of DllMain()!" from the haskell.org wiki, with some minor editing. --- docs/users_guide/ffi-chap.xml | 150 +++++++++++++++++++++++++++------------ docs/users_guide/win32-dlls.xml | 118 ++++++++++++++++++++++++++++-- 2 files changed, 214 insertions(+), 54 deletions(-) diff --git a/docs/users_guide/ffi-chap.xml b/docs/users_guide/ffi-chap.xml index 82f3899..96cbd59 100644 --- a/docs/users_guide/ffi-chap.xml +++ b/docs/users_guide/ffi-chap.xml @@ -10,37 +10,25 @@ Foreign function interface (FFI) Addendum 1.0, whose definition is available from http://haskell.org/. To enable FFI support in GHC, give the - flag, or + flag, or the flag which implies . - The FFI support in GHC diverges from the Addendum in the following ways: - - - - Syntactic forms and library functions proposed in earlier versions - of the FFI are still supported for backwards compatibility. - - - - GHC implements a number of GHC-specific extensions to the FFI - Addendum. These extensions are described in , but please note that programs using - these features are not portable. Hence, these features should be - avoided where possible. - - + GHC implements a number of GHC-specific extensions to the FFI + Addendum. These extensions are described in , but please note that programs using + these features are not portable. Hence, these features should be + avoided where possible. The FFI libraries are documented in the accompanying library - documentation; see for example the Foreign - module. + documentation; see for example the + Foreign module. GHC extensions to the FFI Addendum The FFI features that are described in this section are specific to - GHC. Avoid them where possible to not compromise the portability of the - resulting code. + GHC. Your code will not be portable to other compilers if you use them. Unboxed types @@ -78,7 +66,6 @@ OK: - @@ -137,6 +124,13 @@ extern HsInt foo(HsInt a0); option; see . + When linking the program, remember to include + M_stub.o in the final link command line, or + you'll get link errors for the missing function(s) (this isn't + necessary when building your program with ghc + ––make, as GHC will automatically link in the + correct bits). + Using your own <literal>main()</literal> @@ -188,10 +182,10 @@ int main(int argc, char *argv[]) The call to hs_init() initializes GHC's runtime system. Do NOT try to invoke any Haskell functions before calling - hs_init(): strange things will + hs_init(): bad things will undoubtedly happen. - We pass argc and + We pass references to argc and argv to hs_init() so that it can separate out any arguments for the RTS (i.e. those arguments between @@ -251,10 +245,8 @@ int main(int argc, char *argv[]) After we've finished invoking our Haskell functions, we - can call hs_exit(), which - terminates the RTS. It runs any outstanding finalizers and - generates any profiling or stats output that might have been - requested. + can call hs_exit(), which terminates the + RTS. There can be multiple calls to hs_init(), but each one should be matched @@ -273,23 +265,87 @@ int main(int argc, char *argv[]) to the Main Haskell module. - - Using <literal>foreign import ccall "wrapper"</literal> with GHC + + Making a Haskell library that can be called from foreign + code - foreign import - ccall "wrapper"with GHC - + The scenario here is much like in , except that the aim is not to link a complete program, but to + make a library from Haskell code that can be deployed in the same + way that you would deploy a library of C code. - When foreign import ccall "wrapper" is used - in a Haskell module, The C stub file M_stub.c - generated by GHC contains small helper functions used by the code - generated for the imported wrapper, so it must be linked in to the - final program. When linking the program, remember to include - M_stub.o in the final link command line, or - you'll get link errors for the missing function(s) (this isn't - necessary when building your program with ghc - ––make, as GHC will automatically link in the - correct bits). + The main requirement here is that the runtime needs to be + initialized before any Haskell code can be called, so your library + should provide initialisation and deinitialisation entry points, + implemented in C or C++. For example: + + + HsBool mylib_init(void){ + int argc = ... + char *argv[] = ... + + // Initialize Haskell runtime + hs_init(&argc, &argv); + + // Tell Haskell about all root modules + hs_add_root(__stginit_Foo); + + // do any other initialization here and + // return false if there was a problem + return HS_BOOL_TRUE; + } + + void mylib_end(void){ + hs_exit(); + } + + + The intialisation routine, mylib_init, calls + hs_init() and hs_add_root() as + normal to initialise the Haskell runtime, and the corresponding + deinitialisation funtion mylib_end() calls + hs_exit() to shut down the runtime. + + + + On the use of <literal>hs_exit()</literal> + + hs_exit() normally causes the termination of + any running Haskell threads in the system, and when + hs_exit() returns, there will be no more Haskell + threads running. The runtime will then shut down the system in an + orderly way, generating profiling + output and statistics if necessary, and freeing all the memory it + owns. + + It isn't always possible to terminate a Haskell thread forcibly: + for example, the thread might be currently executing a foreign call, + and we have no way to force the foreign call to complete. What's + more, the runtime must + assume that in the worst case the Haskell code and runtime are about + to be removed from memory (e.g. if this is a Windows DLL, + hs_exit() is normally called before unloading the + DLL). So hs_exit() must wait + until all outstanding foreign calls return before it can return + itself. + + The upshot of this is that if you have Haskell threads that are + blocked in foreign calls, then hs_exit() may hang + (or possibly busy-wait) until the calls return. Therefore it's a + good idea to make sure you don't have any such threads in the system + when calling hs_exit(). This includes any threads + doing I/O, because I/O may (or may not, depending on the + type of I/O and the platform) be implemented using blocking foreign + calls. + + The GHC runtime treats program exit as a special case, to avoid + the need to wait for blocked threads when a standalone + executable exits. Since the program and all its threads are about to + terminate at the same time that the code is removed from memory, it + isn't necessary to ensure that the threads have exited first. + (Unofficially, if you want to use this fast and loose version of + hs_exit(), then call + shutdownHaskellAndExit() instead). @@ -299,7 +355,7 @@ int main(int argc, char *argv[]) C calls, function headers When generating C (using the - directive), one can assist the C compiler in detecting type + flag), one can assist the C compiler in detecting type errors by using the directive () to provide .h files containing function @@ -336,10 +392,10 @@ the module being compiled, you should supply all the options are; but they should be in the package -configuration, which GHC knows about. So if you are building a package, remember -to put all those options into the package configuration. -See the c_includes field in . - +configuration, which GHC knows about. So if you are building a package using + Cabal, remember to put all those include files in the package + description (see the includes field in the Cabal + documentation). It is also possible, according the FFI specification, to put the diff --git a/docs/users_guide/win32-dlls.xml b/docs/users_guide/win32-dlls.xml index 22a77de..f52f189 100644 --- a/docs/users_guide/win32-dlls.xml +++ b/docs/users_guide/win32-dlls.xml @@ -210,8 +210,7 @@ make-sessions running under cygwin. Making Haskell libraries into DLLs doesn't work on Windows at the -moment; however, all the machinery is -still there. If you're interested, contact the GHC team. Note that +moment; we hope to re-instate this facility in the future. Note that building an entire Haskell application as a single DLL is still supported: it's just multi-DLL Haskell programs that don't work. The Windows distribution of GHC contains static libraries only. @@ -403,13 +402,10 @@ non-static to static linking is simply a question of adding Making DLLs to be called from other languages - If you want to package up Haskell code to be called from other languages, such as Visual Basic or C++, there are some extra things it is useful to -know. The dirty details are in the Foreign Function -Interface definition, but it can be tricky to work out how to -combine this with DLL building, so here's an example: - +know. This is a special case of ; we'll deal with + the DLL-specific issues that arise below. Here's an example: @@ -521,6 +517,114 @@ the Haskell source and build the DLL. + +Beware of DllMain()! + +The body of a DllMain() function is an +extremely dangerous place! This is because the order in which DLLs are +unloaded when a process is terminating is unspecified. This means that +the DllMain() for your DLL may be called when other DLLs containing +functions that you call when de-initializing your DLL have already +been unloaded. In other words, you can't put shutdown code inside +DllMain(), unless your shutdown code only requires use of certain +functions which are guaranteed to be available (see the Platform SDK +docs for more info). + +In particular, if you are writing a DLL that's statically +linked with Haskell, it is not safe to call +hs_exit() from DllMain(), since +hs_exit() may make use of other DLLs (see also ). What's more, if you +wait until program shutdown to execute your deinitialisation code, Windows will have +terminated all the threads in your program except the one calling +DllMain(), which can cause even more +problems. + +A solution is to always export Begin() and End() functions from your +DLL, and call these from the application that uses the DLL, so that +you can be sure that all DLLs needed by any shutdown code in your +End() function are available when it is called. + +The following example is untested but illustrates the idea (please let us + know if you find problems with this example or have a better one). Suppose we have a DLL called Lewis which makes use of 2 +Haskell modules Bar and Zap, +where Bar imports Zap and is +therefore the root module in the sense of . Then the main C++ unit for the DLL would +look something like: + + + // Lewis.cpp -- compiled using GCC + #include <Windows.h> + #include "HsFFI.h" + + #define __LEWIS_DLL_EXPORT + #include "Lewis.h" + + #include "Bar_stub.h" // generated by GHC + #include "Zap_stub.h" + + BOOL APIENTRY DllMain( HANDLE hModule, + DWORD ul_reason_for_call, + LPVOID lpReserved + ){ + return TRUE; + } + + extern "C"{ + + LEWIS_API HsBool lewis_Begin(){ + int argc = ... + char *argv[] = ... + + // Initialize Haskell runtime + hs_init(&argc, &argv); + + // Tell Haskell about all root modules + hs_add_root(__stginit_Bar); + + // do any other initialization here and + // return false if there was a problem + return HS_BOOL_TRUE; + } + + LEWIS_API void lewis_End(){ + hs_exit(); + } + + LEWIS_API HsInt lewis_Test(HsInt x){ + // use Haskell functions exported by + // modules Bar and/or Zap + + return ... + } + + } // extern "C" + +and some application which used the functions in the DLL would have a main() function like: + + // MyApp.cpp + #include "stdafx.h" + #include "Lewis.h" + + int main(int argc, char *argv[]){ + if (lewis_Begin()){ + // can now safely call other functions + // exported by Lewis DLL + + } + lewis_End(); + return 0; + } + + +Lewis.h would have to have some appropriate #ifndef to ensure that the +Haskell FFI types were defined for external users of the DLL (who +wouldn't necessarily have GHC installed and therefore wouldn't have +the include files like HsFFI.h etc). + + + -- 1.7.10.4