Clarify the comment.
bcopy() doesn't have a strong spec, so clarify here that it's about
the Bionic implementation.
Change-Id: Icc0e198272b43ae9ccce292ab7f2cdec36a83e49
diff --git a/vm/native/java_lang_System.c b/vm/native/java_lang_System.c
index 4af0dfa..dc04885 100644
--- a/vm/native/java_lang_System.c
+++ b/vm/native/java_lang_System.c
@@ -30,12 +30,13 @@
/* Might overlap. */
if (elemSize == sizeof(Object*)) {
/*
- * In addition to handling overlap properly, bcopy()
- * guarantees atomic treatment of words. This is needed so
- * that concurrent threads never see half-formed pointers
- * or ints. The former is required for proper gc behavior,
- * and the latter is also required for proper high-level
- * language support.
+ * In addition to handling overlap properly, on Bionic
+ * bcopy() guarantees atomic treatment of words, whereas
+ * Bionic memmove() does not (as of this writing).
+ * Atomicity is needed so that concurrent threads never
+ * see half-formed pointers or ints. The former is
+ * required for proper gc behavior, and the latter is also
+ * required for proper high-level language support.
*
* Note: bcopy()'s argument order is different than memcpy().
*/
