[llvm-bugs] [Bug 38632] New: wasm32: atomic_notify intrinsic disagrees with Gecko/wabt implementations

via llvm-bugs llvm-bugs at lists.llvm.org
Sun Aug 19 22:10:10 PDT 2018


https://bugs.llvm.org/show_bug.cgi?id=38632

            Bug ID: 38632
           Summary: wasm32: atomic_notify intrinsic disagrees with
                    Gecko/wabt implementations
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Backend: WebAssembly
          Assignee: unassignedbugs at nondot.org
          Reporter: alex at crichton.co
                CC: dan433584 at gmail.com, llvm-bugs at lists.llvm.org

Currently the `llvm.wasm.atomic.notify` intrinsic in LLVM looks like:

    declare i64 @llvm.wasm.atomic.notify(i32*, i64)

notable taking i64 for a number of waiters to wake up and returning an i64 for
the number of waiters notified. While this agrees with the current proposed
spec [1] it looks like it disagrees with wabt [2] and with Gecko's
implementation (I got validation errors in Firefox nightly).

Is this something that LLVM needs to update? Or should the spec be updated to
use i32?

[1]:
https://github.com/WebAssembly/threads/blob/master/proposals/threads/Overview.md
[2]:
https://github.com/WebAssembly/wabt/blob/ffe92e6c57fe0ee356c5ae98d0ef0ac6ecfdee27/src/opcode.def#L382

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180820/1bb5895c/attachment.html>


More information about the llvm-bugs mailing list