From 71a5c22c2b635ea903c3ae7d2695ca649b38726f Mon Sep 17 00:00:00 2001
From: Jeffrey Yasskin
Date: Thu, 22 Oct 2009 22:11:22 +0000
Subject: Try r84890 again (adding ValueMap<>), now that I've tested the
compile on gcc-4.4.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@84902 91177308-0d34-0410-b5e6-96231b3b80d8
---
docs/ProgrammersManual.html | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
(limited to 'docs/ProgrammersManual.html')
diff --git a/docs/ProgrammersManual.html b/docs/ProgrammersManual.html
index 68367de0bf..e4e3dc29c3 100644
--- a/docs/ProgrammersManual.html
+++ b/docs/ProgrammersManual.html
@@ -83,6 +83,7 @@ option
"llvm/ADT/StringMap.h"
"llvm/ADT/IndexedMap.h"
"llvm/ADT/DenseMap.h"
+ "llvm/ADT/ValueMap.h"
<map>
Other Map-Like Container Options
@@ -1490,6 +1491,23 @@ inserted into the map) that it needs internally.
+
+
+
+
+ValueMap is a wrapper around a DenseMap mapping
+Value*s (or subclasses) to another type. When a Value is deleted or RAUW'ed,
+ValueMap will update itself so the new version of the key is mapped to the same
+value, just as if the key were a WeakVH. You can configure exactly how this
+happens, and what else happens on these two events, by passing
+a Config
parameter to the ValueMap template.
+
+
+