[Webkit-unassigned] [Bug 152842] New: We should be smarter about inlineCapacities with classes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jan 7 11:30:54 PST 2016


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

            Bug ID: 152842
           Summary: We should be smarter about inlineCapacities with
                    classes
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: keith_miller at apple.com

The inlineCapacity used in our ObjectAllocationProfiles should be on the JSFunction Object rather than in the byte code. This enables us to take the sum of them when computing the inlineCapacity when creating derived classes. An example of where this might benefit us is the following:

class Point2D {
    constructor(x,y) { this.x = x; this.y = y; }
}

class Point3D extends Point2D {
    constructor(x,y,z) { super(x,y); this.z = z; }
}

Currently, the inlineCapacity will be 2 but if we take the sum of the static analyzers results we would get 3.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160107/fd1beee1/attachment-0001.html>


More information about the webkit-unassigned mailing list