[Webkit-unassigned] [Bug 203550] New: [JSC] DateMath should have TimeClipped version
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Oct 28 21:10:51 PDT 2019
https://bugs.webkit.org/show_bug.cgi?id=203550
Bug ID: 203550
Summary: [JSC] DateMath should have TimeClipped version
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: ysuzuki at apple.com
ECMAScript uses milliseconds (double) as its internal representation, but Date constructor and its operation clips this double before actually using it.
As a result, this milliseconds is always within 53bit, and it is always integer. This means that we should use int64_t when calculating GregorianDateTime.
When running instruments profiler, 31% of time is consumed by `fmod`. This is really fun, we should use integers instead.
--
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/20191029/43e18490/attachment.htm>
More information about the webkit-unassigned
mailing list