Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8253284

Zero OrderAccess barrier mappings are incorrect

    Details

    • Subcomponent:
    • Resolved In Build:
      b17

      Backports

        Description

        This happens at least on linux-zero-aarch64:

        $ shipilev-jdk/build/linux-aarch64-zero-release/images/jdk/bin/java -jar jcstress-latest.jar -m quick --jvmArgs "-Xint" -sc 64 -t memeffects.basic.volatiles

        org.openjdk.jcstress.tests.memeffects.basic.volatiles.volatile_byte_double [-Xint]: Observed forbidden state: 1, 0.0 (Seeing set guard, not seeing the updated value)
        org.openjdk.jcstress.tests.memeffects.basic.volatiles.volatile_int_long [-Xint]: Observed forbidden state: 42, 0 (Seeing set guard, not seeing the updated value)
        org.openjdk.jcstress.tests.memeffects.basic.volatiles.volatile_boolean_double [-Xint]: Observed forbidden state: true, 0.0 (Seeing set guard, not seeing the updated value)
        org.openjdk.jcstress.tests.memeffects.basic.volatiles.volatile_char_long [-Xint]: Observed forbidden state: A, 0 (Seeing set guard, not seeing the updated value)

        ...and it seems to happen because orderAccess_linux_zero.hpp defaults to compiler-only barriers for most OrderAccess::* calls.

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  shade Aleksey Shipilev
                  Reporter:
                  shade Aleksey Shipilev
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: