[8u] RFR: nativeInstruction atomicity and correctness of patching

[Andrew Haley]

On 06/07/16 14:01, Anton Kozlov wrote:

> I know it's hard to reason about code you can't see. In case
> NativeGeneralJump still is not good, this patch could be postponed
> and reviewed together with C1 when published.

Perhaps it should be.  It ought to be possible to do the
NativeGeneralJump in a way that doesn't require any deep magic or
undefined behaviour, even if it ends up being slightly slower.

I don't want to get in your way, but I have to say when I'm not
convinced.  I'll withdraw my objection now because I know that this
code won't be called from anywhere, but we must revisit this with the
C1 patch.

Andrew.