Changeset 287575 in webkit


Ignore:
Timestamp:
Jan 4, 2022, 10:10:42 AM (4 years ago)
Author:
ysuzuki@apple.com
Message:

WebAssembly i32.atomic.wait timeout value incorrectly interpreted by factor 1000
https://bugs.webkit.org/show_bug.cgi?id=234833

Reviewed by Michael Saboff.

Wasm atomics' timeout should be interpreted as nanoseconds.

  • wasm/WasmOperations.cpp:

(JSC::Wasm::wait):

Location:
trunk/Source/JavaScriptCore
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/ChangeLog

    r287561 r287575  
     12022-01-04  Yusuke Suzuki  <ysuzuki@apple.com>
     2
     3        WebAssembly i32.atomic.wait timeout value incorrectly interpreted by factor 1000
     4        https://bugs.webkit.org/show_bug.cgi?id=234833
     5
     6        Reviewed by Michael Saboff.
     7
     8        Wasm atomics' timeout should be interpreted as nanoseconds.
     9
     10        * wasm/WasmOperations.cpp:
     11        (JSC::Wasm::wait):
     12
    1132022-01-03  Yusuke Suzuki  <ysuzuki@apple.com>
    214
  • trunk/Source/JavaScriptCore/wasm/WasmOperations.cpp

    r287513 r287575  
    828828{
    829829    Seconds timeout = Seconds::infinity();
    830     if (timeoutInNanoseconds >= 0) {
    831         int64_t timeoutInMilliseconds = timeoutInNanoseconds / 1000;
    832         timeout = Seconds::fromMilliseconds(timeoutInMilliseconds);
    833     }
     830    if (timeoutInNanoseconds >= 0)
     831        timeout = Seconds::fromNanoseconds(timeoutInNanoseconds);
    834832    bool didPassValidation = false;
    835833    ParkingLot::ParkResult result;
Note: See TracChangeset for help on using the changeset viewer.