...
Created attachment 401093 [details] Patch
Comment on attachment 401093 [details] Patch r=me
Comment on attachment 401093 [details] Patch Can you add FIXME with URL to enable these tests?
Comment on attachment 401093 [details] Patch Why not just turn on Options::useB3HoistLoopInvariantValues?
Created attachment 401097 [details] Patch
Committed r262666: <https://trac.webkit.org/changeset/262666> All reviewed patches have been landed. Closing bug and clearing flags on attachment 401097 [details].
<rdar://problem/64054082>
Comment on attachment 401097 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=401097&action=review > Source/JavaScriptCore/b3/testb3_1.cpp:783 > + Options::useB3HoistLoopInvariantValues() = true; You probably want to set this back to false after running LICM tests, right? I guess thinking about it there is definitely some weird raciness here since these tests are all run on another thread. Makes me think the most comprehensive solution is to have a bit on procedure that determines if LICM runs.
Comment on attachment 401097 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=401097&action=review >> Source/JavaScriptCore/b3/testb3_1.cpp:783 >> + Options::useB3HoistLoopInvariantValues() = true; > > You probably want to set this back to false after running LICM tests, right? I guess thinking about it there is definitely some weird raciness here since these tests are all run on another thread. Makes me think the most comprehensive solution is to have a bit on procedure that determines if LICM runs. Good point. Maybe the tests should just turn LICM all the time instead of just here. Is there any reason why we won't want to do that?
(In reply to Mark Lam from comment #9) > Comment on attachment 401097 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=401097&action=review > > >> Source/JavaScriptCore/b3/testb3_1.cpp:783 > >> + Options::useB3HoistLoopInvariantValues() = true; > > > > You probably want to set this back to false after running LICM tests, right? I guess thinking about it there is definitely some weird raciness here since these tests are all run on another thread. Makes me think the most comprehensive solution is to have a bit on procedure that determines if LICM runs. > > Good point. Maybe the tests should just turn LICM all the time instead of > just here. Is there any reason why we won't want to do that? Yeah but note that setting Options means you will affect other tests too since they’re run concurrently