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

Andrew Haley aph at redhat.com
Tue Jan 26 19:08:00 UTC 2016

On 01/26/2016 07:04 PM, John Rose wrote:
> Unsafe.copyMemory bottoms out to Copy::conjoint_memory_atomic.
> IMO that's a better starting point than memcpy.  Perhaps it can be
> given an additional parameter (or overloading) to specify a swap size.

OK, but conjoint_memory_atomic doesn't guarantee that destination
words won't be torn if their source is misaligned: in fact it
guarantees that they will will be.


More information about the hotspot-dev mailing list