From 80626e947f2a266a62356c4e1e16b1c0e9e4dc8a Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Tue, 14 Mar 2006 20:02:51 +0000 Subject: [PATCH] Update this to match the documentation in the GC doc and to match actual practice. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@26766 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/LangRef.html | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/docs/LangRef.html b/docs/LangRef.html index 0dd26bfee6d..160a3e251ad 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -2917,7 +2917,7 @@ the runtime to find the pointer at GC safe points.
Syntax:
-  declare sbyte* %llvm.gcread(sbyte** %Ptr)
+  declare sbyte* %llvm.gcread(sbyte* %ObjPtr, sbyte** %Ptr)
 
Overview:
@@ -2928,8 +2928,10 @@ barriers.

Arguments:
-

The argument is the address to read from, which should be an address -allocated from the garbage collector.

+

The second argument is the address to read from, which should be an address +allocated from the garbage collector. The first object is a pointer to the +start of the referenced object, if needed by the language runtime (otherwise +null).

Semantics:
@@ -2950,7 +2952,7 @@ garbage collector runtime, as needed.

Syntax:
-  declare void %llvm.gcwrite(sbyte* %P1, sbyte** %P2)
+  declare void %llvm.gcwrite(sbyte* %P1, sbyte* %Obj, sbyte** %P2)
 
Overview:
@@ -2961,8 +2963,10 @@ barriers (such as generational or reference counting collectors).

Arguments:
-

The first argument is the reference to store, and the second is the heap -location to store to.

+

The first argument is the reference to store, the second is the start of the +object to store it to, and the third is the address of the field of Obj to +store to. If the runtime does not require a pointer to the object, Obj may be +null.

Semantics: