Home | History | Annotate | only in /dalvik/vm/native
Up to higher level directory
NameDateSize
dalvik_bytecode_OpcodeInfo.cpp15-Nov-20111.3K
dalvik_system_DexFile.cpp15-Nov-201116.6K
dalvik_system_VMDebug.cpp15-Nov-201122.5K
dalvik_system_VMRuntime.cpp15-Nov-20117.4K
dalvik_system_VMStack.cpp15-Nov-20117.1K
dalvik_system_Zygote.cpp15-Nov-201115.3K
InternalNative.cpp15-Nov-20118.3K
InternalNative.h15-Nov-20111.1K
InternalNativePriv.h15-Nov-20114.9K
java_lang_Class.cpp15-Nov-201126.5K
java_lang_Double.cpp15-Nov-20111.3K
java_lang_Float.cpp15-Nov-20111.3K
java_lang_Math.cpp15-Nov-20112K
java_lang_Object.cpp15-Nov-20113K
java_lang_reflect_AccessibleObject.cpp15-Nov-20111.5K
java_lang_reflect_Array.cpp15-Nov-20114.6K
java_lang_reflect_Constructor.cpp15-Nov-20112.6K
java_lang_reflect_Field.cpp15-Nov-201124.7K
java_lang_reflect_Method.cpp15-Nov-20118.1K
java_lang_reflect_Proxy.cpp15-Nov-20111.5K
java_lang_Runtime.cpp15-Nov-20114K
java_lang_String.cpp15-Nov-20112.1K
java_lang_System.cpp15-Nov-201112K
java_lang_Throwable.cpp15-Nov-20111.9K
java_lang_VMClassLoader.cpp15-Nov-20115.8K
java_lang_VMThread.cpp15-Nov-20116.8K
java_util_concurrent_atomic_AtomicLong.cpp15-Nov-20111.1K
org_apache_harmony_dalvik_ddmc_DdmServer.cpp15-Nov-20111.4K
org_apache_harmony_dalvik_ddmc_DdmVmInternal.cpp15-Nov-20114.9K
org_apache_harmony_dalvik_NativeTestTarget.cpp15-Nov-20111.2K
README.txt15-Nov-20111.2K
sun_misc_Unsafe.cpp15-Nov-201112.3K

README.txt

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