194079 2019-01-30 22:29:10 -0800 Remove optLevel from B3 2019-02-01 14:53:12 -0800 1 1 1 Unclassified WebKit JavaScriptCore WebKit Nightly Build Unspecified Unspecified NEW P2 Normal --- 191802 1 rmorisset rmorisset saam oldest_to_newest 1500432 0 rmorisset 2019-01-30 22:29:10 -0800 Now that the BBQ tier for WASM goes directly to Air, there is no more need for different optimization tiers inside B3. Both FTL and Warm OMG use B3 -O2. 1500466 1 saam 2019-01-30 23:39:30 -0800 (In reply to Robin Morisset from comment #0) > Now that the BBQ tier for WASM goes directly to Air, there is no more need > for different optimization tiers inside B3. Both FTL and Warm OMG use B3 -O2. I think it might be worth keeping this running just in case we find a use for it in the future. 1501206 2 rmorisset 2019-02-01 12:05:34 -0800 (In reply to Saam Barati from comment #1) > (In reply to Robin Morisset from comment #0) > > Now that the BBQ tier for WASM goes directly to Air, there is no more need > > for different optimization tiers inside B3. Both FTL and Warm OMG use B3 -O2. > > I think it might be worth keeping this running just in case we find a use > for it in the future. I am a bit wary of keeping dead code in the codebase, especially as it will no longer be tested going forward (unless we run extra copies of our tests with different optimization levels, but that sounds like it would heavily increase our already massive testing time). If we find a use for it later, would it be that much of a burden to reinstate it? 1501304 3 saam 2019-02-01 14:53:12 -0800 (In reply to Robin Morisset from comment #2) > (In reply to Saam Barati from comment #1) > > (In reply to Robin Morisset from comment #0) > > > Now that the BBQ tier for WASM goes directly to Air, there is no more need > > > for different optimization tiers inside B3. Both FTL and Warm OMG use B3 -O2. > > > > I think it might be worth keeping this running just in case we find a use > > for it in the future. > > I am a bit wary of keeping dead code in the codebase, especially as it will > no longer be tested going forward (unless we run extra copies of our tests > with different optimization levels, but that sounds like it would heavily > increase our already massive testing time). We already do this > > If we find a use for it later, would it be that much of a burden to > reinstate it?