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

C1 doesn't respect the JMM with volatile field loads

    XMLWordPrintable

Details

    • 6
    • b14
    • generic
    • generic
    • Verified

    Backports

      Description

        A post on hotspot-compiler-dev shows a problem with volatile field loads in C1:

        http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2012-May/007698.html

        The failing test case is:

        public class Test {
            volatile static private int a;
            static private int b;

            public static void main(String [] args) throws Exception {
                for (int i = 0; i < 100; i++) {
                    new Thread() {

                        @Override
                        public void run() {
                            int tt = b; // makes the jvm cache the value of b

                            while (a==0) {

                            }

                            if (b == 0) {
                                System.out.println("error");
                            }
                        }

                    }.start();
                }

                b = 1;
                a = 1;
            }
        }

        To hit the bug run:

        $ java -client Test

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2224998 C1 doesn't respect the JMM with volatile field loads

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2224999 C1 doesn't respect the JMM with volatile field loads

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2225507 C1 doesn't respect the JMM with volatile field loads

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2225824 C1 doesn't respect the JMM with volatile field loads

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8002571 C1 doesn't respect the JMM with volatile field loads

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8002572 C1 doesn't respect the JMM with volatile field loads

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8017365 C1 doesn't respect the JMM with volatile field loads

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8018259 C1 doesn't respect the JMM with volatile field loads

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed
            duplicates

            Bug - A problem which impairs or prevents the functions of the product. JDK-7170319 Bug in GVN code in C1 breaks Java volatile semantics

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8175887 C1 value numbering handling of Unsafe.get*Volatile is incorrect

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Activity

              People

                twisti Christian Thalinger
                twisti Christian Thalinger
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: