src/share/vm/opto/doCall.cpp

rev 6132 : 8007988: PrintInlining output is inconsistent with incremental inlining
Summary: fix duplicate and conflicting inlining output
Reviewed-by:
rev 6133 : 8005079: fix LogCompilation for incremental inlining
Summary: report late inlining as part of the rest of the inlining output
Reviewed-by:
rev 6134 : [mq]: logcompilation-reviews

*** 101,110 ****
--- 101,113 ----
        log->print(" receiver='%d' receiver_count='%d'", rid, receiver_count);
        if (profile.has_receiver(1)) {
          log->print(" receiver2='%d' receiver2_count='%d'", r2id, profile.receiver_count(1));
        }
      }
+     if (callee->is_method_handle_intrinsic()) {
+       log->print(" method_handle_intrinsic='1'");
+     }
      log->end_elem();
    }
  
    // Special case the handling of certain common, profitable library
    // methods.  If these methods are replaced with specialized code,
*** 294,303 ****
--- 297,307 ----
    // There was no special inlining tactic, or it bailed out.
    // Use a more generic tactic, like a simple call.
    if (call_does_dispatch) {
      const char* msg = "virtual call";
      if (PrintInlining) print_inlining(callee, jvms->depth() - 1, jvms->bci(), msg);
+     C->log_inline_failure(msg);
      return CallGenerator::for_virtual_call(callee, vtable_index);
    } else {
      // Class Hierarchy Analysis or Type Profile reveals a unique target,
      // or it is a static or special call.
      return CallGenerator::for_direct_call(callee, should_delay_inlining(callee, jvms));