History log of /dalvik/vm/oo/ObjectInlines.h
Revision Date Author Comments
f16cfefc199d1416c5f83446c1d299786accc737 19-Aug-2010 Andy McFadden <fadden@android.com> Properly handle volatile field accesses from JNI.

For uniprocessors, we need to use the 64-bit quasiatomic functions. For
SMP, we need to do that and also issue barriers on all operations.

This was mostly a matter of adding a bunch of inline getter/setter
functions and then calling the right one based on whether or not the
field is declared volatile.

Also, corrected the output for a failing CHECK_CLASS test in CheckJNI.

Bug 2890631.

(cherry-pick from dalvik-dev)

Change-Id: I3da3b70c906eddd5934347caea83ab041d22cd68
4ac66a9db181df9ab3a12e2c3f928e43bb962344 09-Jul-2010 Barry Hayes <bhayes@google.com> Make the write barrier calls in ObjectInlines conditional; if the
value being stored is NULL, no write barrier call is needed.

Change-Id: I608f9706c233717b4fa0f79f78f152a2a360ee78
0dfa7bff98a5ec755536d54e65362ec3a2b5c49a 25-Jun-2010 Barry Hayes <bhayes@google.com> Fixing up #ifndef inlcude name.

Change-Id: I0dd2f8c18aaaf4cea7b7a6df44e42f889af90ed6
7ef0755c91caeea2cc89d886e566e71dc626abed 25-Jun-2010 Barry Hayes <bhayes@google.com> Move WriteBarrier operations into their own header file. Split Object.h

The write barrier routines will soon be INLINE and non-null. Buried
in the middle of Object.h, which is early in Dalvik.h, it would be
hard for them to make use of definitions in other .h files.

Change-Id: I3c0eb59cb6ef29c2bacd0432cf59aaca4c3d031c