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

compilers test wrong JVMTI flag for enabling deoptimization

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2
    • Resolution: Not an Issue
    • Affects Version/s: 5.0
    • Fix Version/s: None
    • Component/s: hotspot
    • Subcomponent:
    • CPU:
      generic
    • OS:
      generic

      Description

      The test

      JvmtiExport::can_hotswap_or_post_breakpoint()

      is used instead of

      JvmtiExport::can_examine_or_deopt_anywhere()

      in the following two places:

      c1/c1_GraphBuilder.cpp --
              // Register dependence if JVMTI has either breakpoint
              // setting or hotswapping of methods capabilities since they may
              // cause deoptimization.
              if (JvmtiExport::can_hotswap_or_post_breakpoint() && !dependency_recorded) {
                add_dependent(actual_recv, inline_target);
              }
              return;


      opto/parse1.cpp --
          // Always register dependence if JVMDI is enabled, because
          // either breakpoint setting or hotswapping of methods may
          // cause deoptimization.
          if (JvmtiExport::can_hotswap_or_post_breakpoint()) {
            C->recorder()->add_dependent(NULL, method());
          }

      This could cause random behavior or crashes if only the monitor,
      methed entry, etc. capabilities are used. The comments also,
      clearly, need an update.
      ###@###.### 2004-02-24

        Attachments

          Activity

            People

            • Assignee:
              rfield Robert Field
              Reporter:
              rfield Robert Field
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Imported:
                Indexed: