On Jan 26, 2016, at 1:04 AM, Andrew Haley <a...@redhat.com> wrote: > > I agree that memcpy is the right thing to use. It's portable and is > inlined well on production-quality C compilers.
But it is not strong enough to uphold the Java memory model, because it is allows to copy byte-wise, which can tear shorts, ints, or longs, creating illegal race states. So we try to avoid memcpy when we can. — John
