Index: doc/bibliography/pl.bib
===================================================================
--- doc/bibliography/pl.bib	(revision 860f19f8e4e35fd97620e0da5e6c37a54a001484)
+++ doc/bibliography/pl.bib	(revision 200b2b5113c2555b8ba8f43de3ba4e59f17c7dfe)
@@ -1020,4 +1020,21 @@
     year	= 1985,
     pages	= {14-22}
+}
+
+@inproceedings{Necula02,
+    author = {Necula, George C. and McPeak, Scott and Weimer, Westley},
+    title = {{CCured}: Type-safe Retrofitting of Legacy Code},
+    booktitle = {Proceedings of the 29th ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages},
+    series = {POPL '02},
+    year = {2002},
+    isbn = {1-58113-450-9},
+    location = {Portland, Oregon},
+    pages = {128--139},
+    numpages = {12},
+    url = {http://doi.acm.org/10.1145/503272.503286},
+    doi = {10.1145/503272.503286},
+    acmid = {503286},
+    publisher = {ACM},
+    address = {New York, NY, USA},
 }
 
@@ -3653,4 +3670,22 @@
   year={2012},
   organization={IEEE}
+}
+
+@inproceedings{DeLozier13,
+    author = {DeLozier, Christian and Eisenberg, Richard and Nagarakatte, Santosh and Osera, Peter-Michael and Martin, Milo M.K. and Zdancewic, Steve},
+    title = {{I}ronclad {C++}: A Library-augmented Type-safe Subset of {C++}},
+    booktitle = {Proceedings of the 2013 ACM SIGPLAN International Conference on Object Oriented Programming Systems Languages \& Applications},
+    series = {OOPSLA '13},
+    year = {2013},
+    isbn = {978-1-4503-2374-1},
+    location = {Indianapolis, Indiana, USA},
+    pages = {287--304},
+    numpages = {18},
+    url = {http://doi.acm.org/10.1145/2509136.2509550},
+    doi = {10.1145/2509136.2509550},
+    acmid = {2509550},
+    publisher = {ACM},
+    address = {New York, NY, USA},
+    keywords = {c++, local pointers, memory safety, type-safety},
 }
 
Index: doc/papers/general/Paper.tex
===================================================================
--- doc/papers/general/Paper.tex	(revision 860f19f8e4e35fd97620e0da5e6c37a54a001484)
+++ doc/papers/general/Paper.tex	(revision 200b2b5113c2555b8ba8f43de3ba4e59f17c7dfe)
@@ -2737,8 +2737,7 @@
 Objective-C and Cyclone are two other extensions to C with different design goals than \CFA, as discussed above. 
 Other languages extend C with more focused features. 
-CUDA~\cite{Nickolls08}, ispc~\cite{Pharr12}, and Sierra~\cite{Leissa14} add data-parallel primitives to C or \CC;
-such features have not yet been added to \CFA, but are easily incorporated within its design.
-Finally, some C extensions (or suggested extensions) attempt to provide a more memory-safe C~\cite{Boehm88,Rafkind09};
-type-checked polymorphism in \CFA covers several of C's memory-safety issues, but more aggressive approaches such as annotating all pointer types with their nullability are contradictory to \CFA's backwards compatibility goals.
+$\mu$\CC~\cite{uC++book}, CUDA~\cite{Nickolls08}, ispc~\cite{Pharr12}, and Sierra~\cite{Leissa14} add concurrent or data-parallel primitives to C or \CC;
+data-parallel features have not yet been added to \CFA, but are easily incorporated within its design, while concurrency primitives similar to those in $\mu$\CC have already been added~\cite{Delisle18}.
+Finally, CCured~\cite{Necula02} and Ironclad \CC~\cite{DeLozier13} attempt to provide a more memory-safe C by annotating pointer types with garbage collection information; type-checked polymorphism in \CFA covers several of C's memory-safety issues, but more aggressive approaches such as annotating all pointer types with their nullability or requiring runtime garbage collection are contradictory to \CFA's backwards compatibility goals.