Bug 171931 - WebAssemby: builder doesn't do Memory section maximum correctly
Summary: WebAssemby: builder doesn't do Memory section maximum correctly
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: JF Bastien
URL:
Keywords:
Depends on:
Blocks: 161709
  Show dependency treegraph
 
Reported: 2017-05-10 10:38 PDT by JF Bastien
Modified: 2017-05-10 11:22 PDT (History)
7 users (show)

See Also:


Attachments
patch (4.16 KB, patch)
2017-05-10 10:40 PDT, JF Bastien
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description JF Bastien 2017-05-10 10:38:18 PDT
It gets confused by 0 maximum because it's falsy, like undefined.
Comment 1 JF Bastien 2017-05-10 10:40:27 PDT
Created attachment 309616 [details]
patch
Comment 2 Keith Miller 2017-05-10 10:42:07 PDT
Comment on attachment 309616 [details]
patch

r=me.
Comment 3 WebKit Commit Bot 2017-05-10 11:22:34 PDT
Comment on attachment 309616 [details]
patch

Clearing flags on attachment: 309616

Committed r216598: <http://trac.webkit.org/changeset/216598>
Comment 4 WebKit Commit Bot 2017-05-10 11:22:35 PDT
All reviewed patches have been landed.  Closing bug.