[prev in list] [next in list] [prev in thread] [next in thread] 

List:       webkit-unassigned
Subject:    [Webkit-unassigned] [Bug 145496] New: Any exit from any JIT due to profiling for an inline cache sho
From:       bugzilla-daemon () webkit ! org
Date:       2015-05-31 5:34:46
Message-ID: bug-145496-2851 () https ! bugs ! webkit ! org/
[Download RAW message or body]

--1433050471.F7fA0.22219
Date: Sat, 30 May 2015 22:34:31 -0700
MIME-Version: 1.0
Content-Type: text/plain

https://bugs.webkit.org/show_bug.cgi?id=145496

            Bug ID: 145496
           Summary: Any exit from any JIT due to profiling for an inline
                    cache should force all future compilations to be weary
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned@lists.webkit.org
          Reporter: fpizlo@apple.com

Previously we had this thing where the FTL would ignore non-FTL exit sites.  That \
seemed like a good idea at the time, but there are some pathologies that we found in \
Speedometer where this isn't so good.  For example we might have an exit from the DFG \
that happened just after the FTL compilation was enqueued.

-- 
You are receiving this mail because:
You are the assignee for the bug.
--1433050471.F7fA0.22219
Date: Sat, 30 May 2015 22:34:31 -0700
MIME-Version: 1.0
Content-Type: text/html

<html>
    <head>
      <base href="https://bugs.webkit.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Any exit from any JIT due to profiling for an inline cache should \
force all future compilations to be weary"  \
href="https://bugs.webkit.org/show_bug.cgi?id=145496">145496</a>  </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Any exit from any JIT due to profiling for an inline cache should force \
all future compilations to be weary  </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>WebKit
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>528+ (Nightly build)
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P2
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>JavaScriptCore
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>webkit-unassigned&#64;lists.webkit.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>fpizlo&#64;apple.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Previously we had this thing where the FTL would ignore non-FTL exit \
sites.  That seemed like a good idea at the time, but there are some pathologies that \
we found in Speedometer where this isn't so good.  For example we might have an exit \
from the DFG that happened just after the FTL compilation was enqueued.</pre>  </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>
--1433050471.F7fA0.22219--



_______________________________________________
webkit-unassigned mailing list
webkit-unassigned@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-unassigned


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic