[Webkit-unassigned] [Bug 177392] WebAssemly + gigacage maxNumWebAssemblyFastMemories = 10 fails

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Sep 22 17:07:35 PDT 2017


--- Comment #3 from Filip Pizlo <fpizlo at apple.com> ---
(In reply to JF Bastien from comment #2)
> (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...

It is not a goal of options processing to catch all nonsensical inputs. Also, the right maximum here is terribly difficult to deduce.

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/20170923/2ce27cb9/attachment-0001.html>

More information about the webkit-unassigned mailing list