IV26976: VOLATILE VARIABLE INCORRECTLY CACHED ACROSS LOOP ITERATIONS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Error Message: Most likely outcome is deadlock, if one thread is
    looping waiting for a volatile variable to be changed by another
    thread.
    .
    Stack Trace: N/A
    .
    

Local fix

  • -Xjit:disableLoopVersioner
    

Problem summary

  • Loop versioner neglected to check whether an expression included
    a load of a volatile variable before pulling it out of the loop.
    

Problem conclusion

  • This defect will be fixed in:
    7.0.0 SR2
    6.0.1 SR3
    .
    Loop versioner has been changed to leave volatile variables
    alone.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV26976

  • Reported component name

    JIT

  • Reported component ID

    620700124

  • Reported release

    260

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-24

  • Closed date

    2012-08-24

  • Last modified date

    2012-08-24

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    JIT

  • Fixed component ID

    620700124

Applicable component levels

  • R260 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Runtimes for Java Technology
Just In Time (JIT) Compiler

Software version:

260

Reference #:

IV26976

Modified date:

2012-08-24

Translate my page

Machine Translation

Content navigation