diff options
| author | Dietmar Maurer <dietmar@mono-cvs.ximian.com> | 2002-03-15 07:09:44 +0300 |
|---|---|---|
| committer | Dietmar Maurer <dietmar@mono-cvs.ximian.com> | 2002-03-15 07:09:44 +0300 |
| commit | a339ff15f833e4f435161f911678da8b4c951dce (patch) | |
| tree | 664df2746d3e7da53c860d81adffbde7bbb345b8 /docs | |
| parent | 857e4d7b40cad6e260f36ea961727565f51f5c20 (diff) | |
fixed section numbers
svn path=/trunk/mono/; revision=3124
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/unmanaged-calls | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/unmanaged-calls b/docs/unmanaged-calls index 005e2c662bc..55c38ea4561 100644 --- a/docs/unmanaged-calls +++ b/docs/unmanaged-calls @@ -69,7 +69,7 @@ Invoking native (unmanaged) code has several implications: The easiest way to implement this is to always create a wrapper function for PInvoke calls, which takes care of argument marshalling and LMF save/restore. -3.) When/how does the runtime call unmanaged internal calls +4.) When/how does the runtime call unmanaged internal calls We don't need to convert any arguments, so we need only take care of the LMF structure. @@ -120,7 +120,7 @@ But this depends somehow on the calling conventions, and I don't know if that works on all plattforms? -4.) What is stored in the LMF +5.) What is stored in the LMF - all caller saved registers (since we can trust unmanaged code) - the instruction pointer of the last managed instruction |