[Webkit-unassigned] [Bug 82656] New: DFG should optimize a==b for a being an object and b being either an object or null/undefined, and vice versa

[bugzilla-daemon at webkit.org]

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

           Summary: DFG should optimize a==b for a being an object and b
                    being either an object or null/undefined, and vice
                    versa
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: fpizlo at apple.com


V8-raytrace does this.  I figure others might want to do that as well, since it seems like a sensible thing to do.

This bug doesn't extend to going all out and optimizing the case where in a==b both a and b can be either null or object, since I don't yet have evidence that there are enough hot spots in the code out there that do that.

Patch forthcoming.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.