Details
-
Bug
-
Resolution: Fixed
-
P4
-
1.1.6
-
1.2beta4
-
x86
-
windows_95, windows_nt
-
Not verified
Description
Name: tb29552 Date: 05/16/98
When running a set of unit tests with the JIT
enabled, we see four problems:
1) "A nonfatal internal JIT (3.00.039(x)) error
'ReloadFPU64' has occurred in :
'Parse.bCoHortDoubleMethod ()V': Interpreting
method.
Please report this error..."
2) "A nonfatal internal JIT (3.00.039(x)) error
'Unuse64' has occurred in :
'DataRound.run ()V': Interpreting method.
Please report this error..."
3) "A nonfatal internal JIT (3.00.039(x)) error
'GetRegisterA' has occurred in "
'FishersExactTest.sumLnFactorial (IIIII)D':
Interpreting method.
Please report this error..."
4) A bug seemingly related to stack depth
(that is, complex expressions).
The symptom is: a double method which
wrongly returns a number close to zero
(for example, 3.451695E-317, but it varies)
instead of the proper number.
The problem occurs when the return statement
has an expression on it. If you make
a separate statement (double d=<expression>;)
and then return d, there is no error.
This bug does not generate a JIT error
message.
All of these problems occur if the JIT is
turned on. None of these problems occur if
-nojit is used.
The error occur consistly if you rerun the
unit tests.
In the past, we didn't use the JIT, so these
problems may have been in the JIT all along.
This is the first time these unit tests have
been done with the JIT.
I spent a long time trying to make a simple
example of the 4th problem, but I couldn't.
(Review ID: 30473)
======================================================================