NameDateSize

..11-Jul-20144 KiB

dalvik_bytecode_OpcodeInfo.cpp11-Jul-20141.3 KiB

dalvik_system_DexFile.cpp11-Jul-201416.7 KiB

dalvik_system_VMDebug.cpp11-Jul-201424.7 KiB

dalvik_system_VMRuntime.cpp11-Jul-201420.7 KiB

dalvik_system_VMStack.cpp11-Jul-20147.1 KiB

dalvik_system_Zygote.cpp11-Jul-201421.7 KiB

InternalNative.cpp11-Jul-20148.3 KiB

InternalNative.h11-Jul-20141.1 KiB

InternalNativePriv.h11-Jul-20144.9 KiB

java_lang_Class.cpp11-Jul-201428 KiB

java_lang_Double.cpp11-Jul-20141.3 KiB

java_lang_Float.cpp11-Jul-20141.3 KiB

java_lang_Math.cpp11-Jul-20142 KiB

java_lang_Object.cpp11-Jul-20143 KiB

java_lang_reflect_AccessibleObject.cpp11-Jul-20141.5 KiB

java_lang_reflect_Array.cpp11-Jul-20144.6 KiB

java_lang_reflect_Constructor.cpp11-Jul-20142.6 KiB

java_lang_reflect_Field.cpp11-Jul-201424.7 KiB

java_lang_reflect_Method.cpp11-Jul-20148.1 KiB

java_lang_reflect_Proxy.cpp11-Jul-20141.5 KiB

java_lang_Runtime.cpp11-Jul-20144.6 KiB

java_lang_String.cpp11-Jul-20142.1 KiB

java_lang_System.cpp11-Jul-201413.2 KiB

java_lang_Throwable.cpp11-Jul-20141.9 KiB

java_lang_VMClassLoader.cpp11-Jul-20145.8 KiB

java_lang_VMThread.cpp11-Jul-20146.8 KiB

java_util_concurrent_atomic_AtomicLong.cpp11-Jul-20141.1 KiB

org_apache_harmony_dalvik_ddmc_DdmServer.cpp11-Jul-20141.4 KiB

org_apache_harmony_dalvik_ddmc_DdmVmInternal.cpp11-Jul-20144.9 KiB

org_apache_harmony_dalvik_NativeTestTarget.cpp11-Jul-20141.2 KiB

README.txt11-Jul-20141.2 KiB

sun_misc_Unsafe.cpp11-Jul-201412.3 KiB

README.txt

1Internal native functions.
2
3All of the functions defined here make direct use of VM functions or data
4structures, so they can't be written with JNI and shouldn't really be in
5a separate shared library.  Do not add additional functions here unless
6they need to access VM internals directly.
7
8All functions here either complete quickly or are used to enter a wait
9state, so we don't set the thread status to THREAD_NATIVE when executing
10these methods.  This means that the GC will wait for these functions
11to finish.  DO NOT perform long operations or blocking I/O in here.
12These methods should not be declared "synchronized", because we don't
13check for that flag when issuing the call.
14
15We use "late" binding on these, rather than explicit registration,
16because it's easier to handle the core system classes that way.
17
18The functions here use the DalvikNativeFunc prototype, but we can
19also treat them as DalvikBridgeFunc, which takes two extra arguments.
20The former represents the API that we're most likely to expose should
21JNI performance be deemed insufficient.  The Bridge version is used as
22an optimization for a few high-volume Object calls, and should generally
23not be used as we may drop support for it at some point.
24