<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    Thanks Harold.<br>
    Coleen<br>
    <br>
    <div class="moz-cite-prefix">On 4/11/14, 12:25 PM, harold seigel
      wrote:<br>
    </div>
    <blockquote cite="mid:5348178C.4090105@oracle.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      Hi Coleen,<br>
      <br>
      You changes look good.<br>
      <br>
      Harold<br>
      <br>
      <div class="moz-cite-prefix">On 4/11/2014 12:22 PM, Coleen
        Phillimore wrote:<br>
      </div>
      <blockquote cite="mid:534816C4.9070904@oracle.com" type="cite">
        <meta content="text/html; charset=ISO-8859-1"
          http-equiv="Content-Type">
        <br>
        <div class="moz-cite-prefix">On 4/11/14, 12:00 PM, Keith
          McGuigan wrote:<br>
        </div>
        <blockquote
cite="mid:CADNkbOFdTUb8-1=qcTk6=TQPOF5sWiQmg=vVP7OvTiPGDOoDKw@mail.gmail.com"
          type="cite">
          <div dir="ltr">Looks good, but why are you not using a newer
            version of webrev with "next" links??</div>
        </blockquote>
        <br>
        Thanks Keith.  The private copy I had of the "next" link webrev
        that I had broke for me for some mysterious reason.  I filed a
        bug to see if the "official" version of webrev could have "next"
        links instead of debugging my own.<br>
        Thanks!<br>
        Coleen<br>
        <br>
        <blockquote
cite="mid:CADNkbOFdTUb8-1=qcTk6=TQPOF5sWiQmg=vVP7OvTiPGDOoDKw@mail.gmail.com"
          type="cite">
          <div dir="ltr">
            <div><br>
            </div>
            <div>--</div>
            <div>- Keith</div>
          </div>
          <div class="gmail_extra"><br>
            <br>
            <div class="gmail_quote">On Fri, Apr 11, 2014 at 10:48 AM,
              Coleen Phillimore <span dir="ltr"><<a
                  moz-do-not-send="true"
                  href="mailto:coleen.phillimore@oracle.com"
                  target="_blank">coleen.phillimore@oracle.com</a>></span>
              wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">Summary:

                Dtrace monitoring uses size before mirror size is set.<br>
                <br>
                The refactoring I did for bug <a moz-do-not-send="true"
href="https://bugs.openjdk.java.net/browse/JDK-8028497" target="_blank">https://bugs.openjdk.java.net/browse/JDK-8028497</a>
                caused this bug. The size of the mirror is filled in by
                the InstanceMirrorKlass allocation but was used for
                dtrace probes before it in the normal allocation pass.
                 Pass the allocated size to dtrace function instead.<br>
                <br>
                Tested by dtrace tests on solaris sparcv9, testbase
                vm.quick.testlist also.<br>
                <br>
                open webrev at <a moz-do-not-send="true"
                  href="http://cr.openjdk.java.net/%7Ecoleenp/8039904/"
                  target="_blank">http://cr.openjdk.java.net/~coleenp/8039904/</a><br>
                bug link <a moz-do-not-send="true"
                  href="https://bugs.openjdk.java.net/browse/JDK-8039904"
                  target="_blank">https://bugs.openjdk.java.net/browse/JDK-8039904</a><br>
                <br>
                Thanks,<br>
                Coleen<br>
              </blockquote>
            </div>
            <br>
          </div>
        </blockquote>
        <br>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>