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

Andrew Haley aph at redhat.com
Thu May 28 07:58:00 UTC 2015

On 28/05/15 01:06, Jim Graham wrote:
> Where do you see evidence that it can crash?

It's what the language specification says.  Undefined behaviour is
unconstrained: it can do anything.  Demons might fly out of your nose.

We have seen with GCC that apparently "harmless" code (a read just
beyond the end of an array) can, for example, result in an infinite
loop.  In this case, it is quite possible that GCC could infer that
the two memory regions accessed by memcpy do not overlap.


More information about the 2d-dev mailing list