RFR JDK-8141491: Unaligned memory access in Bits.c

[John Rose]

On Jan 26, 2016, at 1:04 AM, Andrew Haley <aph at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/nio-dev/attachments/20160126/bc56917d/attachment.html>