"Type-safety guarantee" is indexed by this tag as well.
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
defer/rcuapi.tex | 2 +-
defer/rcuusage.tex | 2 +-
together/refcnt.tex | 3 ++-
3 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/defer/rcuapi.tex b/defer/rcuapi.tex
index ee939341..c152251b 100644
--- a/defer/rcuapi.tex
+++ b/defer/rcuapi.tex
@@ -242,7 +242,7 @@ The \co{rcu_barrier()} primitive does this job.
}
Finally, RCU may be used to provide
-type-safe memory~\cite{Cheriton96a}, as described in
+\IX{type-safe memory}~\cite{Cheriton96a}, as described in
\cref{sec:defer:Type-Safe Memory}.
In the context of RCU, type-safe memory guarantees that a given
data element will not change type during any RCU read-side critical section
diff --git a/defer/rcuusage.tex b/defer/rcuusage.tex
index f69201bb..a3a17f61 100644
--- a/defer/rcuusage.tex
+++ b/defer/rcuusage.tex
@@ -586,7 +586,7 @@ same type.
In other words, these lockless algorithms can tolerate a given data
element being freed and reallocated as the same type of structure
while they are referencing it, but must prohibit a change in type.
-This guarantee, called ``type-safe memory'' in
+This guarantee, called ``\IX{type-safe memory}'' in
academic literature~\cite{Cheriton96a},
is weaker than the \IXpl{existence guarantee} discussed
in \cref{sec:defer:Existence Guarantee},
diff --git a/together/refcnt.tex b/together/refcnt.tex
index 56c6baa9..1963ddd2 100644
--- a/together/refcnt.tex
+++ b/together/refcnt.tex
@@ -38,7 +38,8 @@ use in concurrent software, including:
garbage collectors, and, as is seen in
\cref{sec:defer:Hazard Pointers,sec:defer:Read-Copy Update (RCU)},
by hazard pointers and RCU, respectively.
-\item A type-safety guarantee is provided for the object.
+\item A \IXalt{type-safety guarantee}{type-safe memory}
+ is provided for the object.
An additional identity check must be performed once
the reference is acquired.
Type-safety guarantees can be provided by special-purpose
--
2.17.1
