RESOLVED FIXED 194145
[JSC] Remove cellJSValueOOBSpace
https://bugs.webkit.org/show_bug.cgi?id=194145
Summary [JSC] Remove cellJSValueOOBSpace
Yusuke Suzuki
Reported 2019-01-31 23:32:43 PST
[JSC] Remove cellJSValueOOBSpace
Attachments
Patch (3.60 KB, patch)
2019-01-31 23:34 PST, Yusuke Suzuki
mark.lam: review+
Yusuke Suzuki
Comment 1 2019-01-31 23:34:06 PST
Mark Lam
Comment 2 2019-02-01 10:02:11 PST
Comment on attachment 360841 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=360841&action=review > Source/JavaScriptCore/ChangeLog:3 > + [JSC] Remove cellJSValueOOBSpace Can you provide some context on why this is needed and appropriate?
Mark Lam
Comment 3 2019-02-01 10:55:23 PST
Comment on attachment 360841 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=360841&action=review >> Source/JavaScriptCore/ChangeLog:3 >> + [JSC] Remove cellJSValueOOBSpace > > Can you provide some context on why this is needed and appropriate? Spoke to Yusuke offline. This subspace does not currently add any value. So, we're removing it.
Yusuke Suzuki
Comment 4 2019-02-01 11:00:00 PST
Radar WebKit Bug Importer
Comment 5 2019-02-01 11:01:01 PST
Saam Barati
Comment 6 2019-02-01 11:17:50 PST
Can we go back to our previous naming of these subspaces too? DangerousBits doesn't make much sense anymore given we're ripping this out.
Yusuke Suzuki
Comment 7 2019-02-01 11:18:59 PST
(In reply to Saam Barati from comment #6) > Can we go back to our previous naming of these subspaces too? DangerousBits > doesn't make much sense anymore given we're ripping this out. Nice catch! I'll do that soon.
Yusuke Suzuki
Comment 8 2019-02-01 11:22:00 PST
(In reply to Yusuke Suzuki from comment #7) > (In reply to Saam Barati from comment #6) > > Can we go back to our previous naming of these subspaces too? DangerousBits > > doesn't make much sense anymore given we're ripping this out. > > Nice catch! I'll do that soon. The previous name was cellSpace.
Yusuke Suzuki
Comment 9 2019-02-01 11:33:26 PST
Note You need to log in before you can comment on or make changes to this bug.