RESOLVED FIXED 165481
Remove old Wasm object model 
https://bugs.webkit.org/show_bug.cgi?id=165481
Summary Remove old Wasm object model
Saam Barati
Reported 2016-12-06 11:19:29 PST
It makes the current code quite confusing to read.
Attachments
patch (49.81 KB, patch)
2016-12-06 12:45 PST, Saam Barati 		keith_miller: review+
DetailsFormatted DiffDiff
patch for landing (49.83 KB, patch)
2016-12-06 14:46 PST, Saam Barati 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Saam Barati
Comment 1 2016-12-06 12:45:46 PST
Created attachment 296309 [details] patch
Keith Miller
Comment 2 2016-12-06 12:47:31 PST
Comment on attachment 296309 [details] patch r=me.
WebKit Commit Bot
Comment 3 2016-12-06 12:48:18 PST
Attachment 296309 [details] did not pass style-queue: ERROR: Source/JavaScriptCore/ChangeLog:7: Line contains tab character. [whitespace/tab] [5] ERROR: Source/JavaScriptCore/llint/LLIntSlowPaths.cpp:1296: One line control clauses should not use braces. [whitespace/braces] [4] Total errors found: 2 in 6 files If any of these errors are false positives, please file a bug against check-webkit-style.
Mark Lam
Comment 4 2016-12-06 12:48:45 PST
Comment on attachment 296309 [details] patch r=me too.
Saam Barati
Comment 5 2016-12-06 14:46:13 PST
Created attachment 296325 [details] patch for landing
WebKit Commit Bot
Comment 6 2016-12-06 14:48:40 PST
Attachment 296325 [details] did not pass style-queue: ERROR: Source/JavaScriptCore/llint/LLIntSlowPaths.cpp:1296: One line control clauses should not use braces. [whitespace/braces] [4] Total errors found: 1 in 6 files If any of these errors are false positives, please file a bug against check-webkit-style.
WebKit Commit Bot
Comment 7 2016-12-06 16:28:26 PST
Comment on attachment 296325 [details] patch for landing Clearing flags on attachment: 296325 Committed r209433: <http://trac.webkit.org/changeset/209433>
WebKit Commit Bot
Comment 8 2016-12-06 16:28:30 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.