From 4d6deb099ee63f2b19f3abbe11e8e3c106fd8493 Mon Sep 17 00:00:00 2001 From: NAKAMURA Takumi Date: Sat, 9 Apr 2011 09:51:57 +0000 Subject: docs/*.html: Make W3C HTML 4.01 Strict more compliant. FIXME: The logo handling in ReleaseNotes.html git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@129208 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/GarbageCollection.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/GarbageCollection.html') diff --git a/docs/GarbageCollection.html b/docs/GarbageCollection.html index d5fe258ba1..bd114b562f 100644 --- a/docs/GarbageCollection.html +++ b/docs/GarbageCollection.html @@ -151,14 +151,14 @@ collector models. For instance, the intrinsics permit:

support a broad class of garbage collected languages including Scheme, ML, Java, C#, Perl, Python, Lua, Ruby, other scripting languages, and more.

-

However, LLVM does not itself provide a garbage collector—this should +

However, LLVM does not itself provide a garbage collector—this should be part of your language's runtime library. LLVM provides a framework for compile time code generation plugins. The role of these plugins is to generate code and data structures which conforms to the binary interface specified by the runtime library. This is similar to the relationship between LLVM and DWARF debugging info, for example. The difference primarily lies in the lack of an established standard in the domain -of garbage collection—thus the plugins.

+of garbage collection—thus the plugins.

The aspects of the binary interface with which LLVM's GC support is concerned are:

-- cgit v1.2.3