[Webkit-unassigned] [Bug 177392] WebAssemly + gigacage maxNumWebAssemblyFastMemories = 10 fails
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Sep 22 16:24:54 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=177392
--- Comment #2 from JF Bastien <jfbastien at apple.com> ---
(In reply to Filip Pizlo from comment #1)
> Not a bug. The purpose of maxNumWebAssemblyFastMemories is to protect us
> from this case by ensuring the we don’t ever eat up all of the gigacage just
> with virtual allocations.
Options processing should catch an invalid input for maxNumWebAssemblyFastMemories then, no? x86 used to be able to have a huge number of fast memories...
--
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/67527578/attachment.html>
More information about the webkit-unassigned
mailing list