[Webkit-unassigned] [Bug 280547] New: [JSC] performJITMemcpy zero-checking's diagnostics should be improved

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Sep 27 15:37:14 PDT 2024


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

            Bug ID: 280547
           Summary: [JSC] performJITMemcpy zero-checking's diagnostics
                    should be improved
           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: marcus_plutowski at apple.com

rdar://136858657

The existing feature checks for the presence of long (>16B) runs of 0-bytes in the output buffer after a JIT memcpy completes.
We also want to know whether the 0s were in the original source buffer, or whether they might have been introduced in the intervening time-period (e.g. during the linking stage). We can do this without performance overhead by checking the source buffer before we crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240927/cf5c1636/attachment.htm>


More information about the webkit-unassigned mailing list