[OpenJDK 2D-Dev] [9] Review Request: 8080847 Copying of overlapping memory should be improved in java2d

Andrew Haley aph at redhat.com
Fri May 29 08:09:04 UTC 2015

On 28/05/15 21:33, Jim Graham wrote:
> The only viable reason for switching to memmove is to either silence the 
> tool that reported the issue or to fix the data ordering issue. 

Or to remove the UB.  Your opinion that UB is constrained is wrong in
principle and dangerous in practice.  It is extrememly unlikely that
moving to memmove() will result in perciptible difference; I can't see
any reason not to simply fix your code.

> There are other ways to silence the tool without making one of our
> blits have behavior that doesn't match other similar blits, and if
> we are going to fix the data ordering issue we should do it for all
> blits...



More information about the 2d-dev mailing list