Toba/JDK Differences

Dynamic Loading

Dynamic loading is supported on platforms that have a JIT compiler: currently only Linux/Intel. On these platforms, the CLASSPATH is searched when a new class is needed, and if found, the class will be loaded and compiled. Preference is given to classes that can be found pre-compiled in the executable or a Toba package. On other platforms, Toba does not support true dynamic loading; all needed classes must be precompiled into the executable or a Toba package. The class java.lang.ClassLoader is not implemented, and java.lang.Class.getClassLoader() always returns null. However, the method java.lang.Class.forName() can find any class referenced directly or indirectly from the main class, and under Solaris, Irix and Linux, it can find any class precompiled into the executable or a Toba package.

System Properties

Toba gives different values for some system properties than the Sun implementation. For example, the os.name and os.version properties give the values returned by the uname system call.

Validation

Toba does not validate class files; it assumes that all class files are properly formatted, contain legal instructions, and obey the specification in all other respects. Malformed class files may produce unpredictable results.

Visibility Checking

Toba does not claim to guard against deliberate deception, so it does not check accesses between different classes. It assumes that the checking performed by javac is sufficient.

Security

Toba does not implement a security manager.

Native Code Interface

The native code interface is incompatible with that of the Sun implementation. (It is actually simpler, and it allows native functions to be overloaded.)

Stack Overflow

The result of stack overflow, such as from infinite recursion, is typically a segmentation fault instead of a Java exception. Errors in any native code can also cause segmentation faults or other symptoms. All other errors result in catchable exceptions.

Debugging

No debugging facilities are implemented. The breakpoint instruction is ignored, and stack traces are not available.

Implementation Differences

Linux

Differences in the Linux implementation:

• Scout threads are a non-preemptible thread model, and starvation-prevention imposes a large overhead on systems that use scout_threads. We are investigating solutions to this.
• The ClassLoader associated with a class by the Class.getClassLoader() method is incorrect when a user class loader defers to the system class loader.
• The following mandated numerical results are not satisfied by jit'd code:
  • Cast of not-a-number to int or long should yield 0.
  • Cast of a float or double larger than Integer.MAX_VALUE to int should yield Integer.MAX_VALUE
  • Cast of a float or double larger than Long.MAX_VALUE to int should yield Long.MAX_VALUE
• The binary encoding of a particular not-a-number float may not be preserved in operations.
• Dividing the largest negative integer by -1 causes an untrapped numeric exception which halts the program.

Irix

Differences in the Irix implementation:

• The binary encoding of a particular not-a-number float may not be preserved in operations.
• Dividing the largest negative integer by -1 causes an untrapped numeric exception which halts the program.

Solaris

There are no additional differences that are specific to Solaris.