tree ac9f6424493fe151e07e38a7da12c49e1cd023e2
parent de805a5f4f9f1f22e086533cfe3f78ebef7a9eed
author Andy McFadden <fadden@android.com> 1287433711 -0700
committer Andy McFadden <fadden@android.com> 1287434048 -0700

Pop call frame before boxing result

After reflective method calls, primitive results need to be boxed
up in an appropriate object.  This generally requires allocating an
object of the appropriate type.  We were doing this before popping
the call frame, which meant that if the allocation caused a GC we
would be scanning results out of a "dead" stack frame.

We hit a case where a register went from holding a reference to
holding a primitive right before the method returned.  The exported
PC was pointing at the last GC point, where the register was expected
to hold a reference, so precise GC was getting very confused.

Bug 3102352.

Change-Id: Ic929b725ab81cbaab4c7aa1d85131f7ca3cec961