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

[TESTBUG] Some forceEarlyReturn00* tests failed due to compiler optimization

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 16
    • 16
    • core-svc
    • None
    • b09

      Following tests which were compiled by GCC 10.2 failed.

        - vmTestbase/nsk/jdi/ThreadReference/forceEarlyReturn/forceEarlyReturn004/forceEarlyReturn004.java
       
       - vmTestbase/nsk/jdwp/ThreadReference/ForceEarlyReturn/forceEarlyReturn002/forceEarlyReturn002.java

      They have native module, and they are commented as below:

      ```
         // execute infinite loop to be sure that thread in native method
         while (always_true)
         {
             // Need some dummy code so the optimizer does not remove this loop.
             dummy_counter = dummy_counter < 1000 ? 0 : dummy_counter + 1;
         }
         // The optimizer can be surprisingly clever.
         // Use dummy_counter so it can never be optimized out.
         // This statement will always return 0.
         return dummy_counter >= 0 ? 0 : 1;
      ```

      C compiler maybe eliminate this loop. We should not consider compiler optimization at this point with other solution.

        1. forceEarlyReturn002.jtr
          27 kB
          Yasumasa Suenaga
        2. forceEarlyReturn004.jtr
          30 kB
          Yasumasa Suenaga

            ysuenaga Yasumasa Suenaga
            ysuenaga Yasumasa Suenaga
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: