2009-02-12 Zoltan Varga <vargaz@gmail.com>

	* call-sites.txt: Remove this, its contents is in jit-trampolines.

svn path=/trunk/mono/; revision=126747

2 files changed, 2 insertions, 27 deletions

diff --git a/docs/ChangeLog b/docs/ChangeLog
index 4742f7c4d63..54f51043b41 100644
--- a/docs/ChangeLog
+++ b/docs/ChangeLog
@@ -1,5 +1,7 @@
 2009-02-12  Zoltan Varga  <vargaz@gmail.com>
 
+	* call-sites.txt: Remove this, its contents is in jit-trampolines.
+
 	* memory-management.txt thread-safety.txt aot-compiler.txt jit-regalloc
 	exception-handling.txt: Remove documents which are now on the wiki.
 
diff --git a/docs/call-sites.txt b/docs/call-sites.txt
deleted file mode 100644
index 5329412d436..00000000000
--- a/docs/call-sites.txt
+++ /dev/null
@@ -1,27 +0,0 @@
-Call Sites
-Extracted from emails from Paolo Molaro
-
-
-There are 3 basic different kinds of call sites:
-
-	1) normal calls:
-	        call relative_displacement
-	
-	2) virtual calls:
-	        call *positive_offset(%register)
-	
-	3) interface calls:
-	        mov constant, %imt_register
-	        call *negative_offset(%register)
-	
-The above is what happens on x86 and amd64, with different values of
-%imt_register for each arch (this register is a constant, but it could
-change with different mono builds, it should be likely one of
-constants the runtime comunicates to the debugger). %register can
-change depending on the callsite based on the register allocator
-choices.  Note that the constant for the interface calls won't
-necessarily be a MonoMethod address: this could change in the future
-to a simple number.
-
-In all the 3 cases the JIT trampolines will need to inspect the call
-site, but only in the first case the call site will be changed.