IV47769: INCORRECT EXIT CONDITIONS FOR CHAR TO BYTE TRANSLATION LOOP
Closed as program error.
Error Message: N/A . Stack Trace: N/A . This problem can only occur on the zOS and zLinux platforms. In a compiled Java method, a loop that translates characters from an input array to an output array of bytes, which has three or more loop exit conditions, may result in the loop translating too few or too many characters. In the latter case, a buffer overflow may occur and cause a GPF or ABEND of the JVM.
This issue can be worked around with the -Xjit:disableIdiomRecognition option.
The problem is caused by a JIT optimization which recognizes the array translation loop, but incorrectly modifies the loop exit conditions, causing prematured or delayed termination of the loop.
This defect will be fixed in: 7.0.0 SR6 6.0.1 SR7 6.0.0 SR15 . The JIT compiler has been updated to adjust the loop exit conditions correctly.
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels