Bug 171931

Summary: WebAssemby: builder doesn't do Memory section maximum correctly
Product: WebKit Reporter: JF Bastien <jfbastien>
Component: JavaScriptCoreAssignee: JF Bastien <jfbastien>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, fpizlo, jfbastien, keith_miller, mark.lam, msaboff, saam
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 161709    
Attachments:
Description Flags
patch none

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.