[Webkit-unassigned] [Bug 177392] New: WebAssemly + gigacage maxNumWebAssemblyFastMemories = 10 fails
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Sep 22 15:27:59 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=177392
Bug ID: 177392
Summary: WebAssemly + gigacage maxNumWebAssemblyFastMemories =
10 fails
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebAssembly
Assignee: webkit-unassigned at lists.webkit.org
Reporter: jfbastien at apple.com
CC: fpizlo at apple.com, jfbastien at apple.com,
keith_miller at apple.com, mark.lam at apple.com,
msaboff at apple.com, rmorisset at apple.com,
sbarati at apple.com
Set maxNumWebAssemblyFastMemories to 10, then run:
./Tools/Scripts/run-javascriptcore-tests --debug --filter=wasm --quick --no-build --no-testapi --no-testmasm --no-testb3 --no-testair
Or just:
(cd ./JSTests/wasm/ && DYLD_FRAMEWORK_PATH=$d/WebKitBuild/$type/ $d/WebKitBuild/$type/jsc -m ./js-api/dont-mmap-zero-byte-memory.js)
This fails in gigacage allocation when trying to allocate a fast memory, because it expects that allocation to succeed and it RELEASE_ASSERTs out. I didn't investigate, but it shouldn't fail (it's a virtual allocation), and it should fall back to slow memory if so.
--
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/20170922/9a612eb4/attachment.html>
More information about the webkit-unassigned
mailing list