I've released IKVM 0.42
to SourceForge. The binaries are identical to the ones in release candidate 3
This document lists the known issues and incompatibilities.
- Code unloading (aka class GC) is not supported.
- In Java static initializers can deadlock, on .NET some threads can see uninitialized state in cases where deadlock would occur on the JVM.
- Only supported in the default AppDomain.
- Only the JNICALL calling convention is supported! (On Windows, HotSpot appears to also support the cdecl calling convention).
- Cannot call string contructors on already existing string instances
- A few limitations in Invocation API support
- The Invocation API is only supported when running on .NET.
- JNI_CreateJavaVM: init options "-verbose[:class|:gc|:jni]", "vfprintf", "exit" and "abort" are not implemented. The JDK 1.1 version of JavaVMInitArgs isn't supported.
- JNI_GetDefaultJavaVMInitArgs not implemented
- JNI_GetCreatedJavaVMs only returns the JavaVM if the VM was started through JNI or a JNI call that retrieves the JavaVM has already occurred.
- DestroyJVM is only partially implemented (it waits until there are no more non-daemon Java threads and then returns JNI_ERR).
- DetachCurrentThread doesn't release monitors held by the thread.
- Native libraries are never unloaded (because code unloading is not supported).
- The JVM allows any reference type to be passed where an interface reference is expected (and to store any reference type in an interface reference type field), on IKVM this results in an IncompatibleClassChangeError.
- monitorenter / monitorexit cannot be used on unitialized this reference.
- Floating point is not fully spec compliant.
- A method returning a boolean that returns an integer other than 0 or 1 behaves differently (this also applies to byte/char/short and for method parameters).
- Synchronized blocks are not async exception safe.
- Ghost arrays don't throw ArrayStoreException when you store an object that doesn't implement the ghost interface.
- Class loading is more eager than on the reference VM.
- Interface implementation methods are never really final (interface can be reimplemented by .NET subclasses).
- JSR-133 finalization spec change is not fully implemented. The JSR-133 changes dictate that an object should not be finalized unless the Object constructor has run successfully, but this isn't implemented.
Static Compiler (ikvmc)
- Some subtle differences with ikvmc compiled code for public members inherited from non-public base classes (so called "access stubs"). Because the access stub lives in a derived class, when accessing a member in a base class, the derived cctor will be run whereas java (and ikvm) only runs the base cctor.
- Try blocks around base class ctor invocation result in unverifiable code (no known compilers produce this type of code).
- Try/catch blocks before base class ctor invocation result in unverifiable code (this actually happens with the Eclipse compiler when you pass a class literal to the base class ctor and compile with -target 1.4).
- Only code compiled in a single assembly fully obeys the JLS binary compatibility rules.
- An assembly can only contain one resource with a particular name.
- Passing incorrect command line options to ikvmc may result in an exception rather than a proper error messages.
Most class library code is based on OpenJDK 6 build 16. Below is a list of divergences and IKVM specific implementation notes.
||GNU Classpath implementation. Not implemented.|
||Partial System.Windows.Forms based back-end. Not supported.|
||No IPv6 support implemented.|
||Getting the default system proxy for a URL is not implemented.|
||GNU Classpath implementation. Not supported.|
||Partially based on GNU Classpath implementation.|
||Partial implementation. JPEGs can be read and written, but there is no metadata support.|
||Implementation based on .NET ODBC managed provider.|
||Audio content handlers not implemented.|
||Image content handlers not implemented.|
The entire public API is available, so "Not implemented." for javax.print, for example, means that the API is there but there is no back-end to provide the actual printing support. "Not supported." means that the code is there and probably works at least somewhat, but that I'm less likely to fix bugs reported in these areas.
Specific API notes:
- java.lang.Thread.stop(Throwable t) doesn't support throwing arbitrary exceptions on other threads (only java.lang.ThreadDeath).
- java.lang.Thread.holdsLock(Object o) causes a spurious notify on the object (this is allowed by the J2SE 5.0 spec).
- java.lang.String.intern() strings are never garbage collected.
- Weak/soft references and reference queues are inefficient and do not fully implement the required semantics.
- java.lang.ref.SoftReference: Soft references are not guaranteed to be cleared before an OutOfMemoryError is thrown.
- Threads started outside of Java aren't "visible" (e.g. in ThreadGroup.enumerate()) until they first call Thread.currentThread().
- java.lang.Thread.getState() returns WAITING or TIMED_WAITING instead of BLOCKING when we're inside Object.wait() and blocking to re-acquire the monitor.
- java.nio.channel.FileChannel.lock() shared locks are only supported on Windows NT derived operating systems.
- java.lang.SecurityManager: Deprecated methods not implemented: classDepth(String), inClass(String), classLoaderDepth(), currentLoadedClass(), currentClassLoader(), inClassLoader()
This release has been tested on the following CLI implementations / platforms:
|.NET 2.0 SP2
|.NET 2.0 SP2
There is experimental support for running in partial trust.