Add test for osr exiting with interpreter on the stack
Created attachment 385406 [details] Patch
Comment on attachment 385406 [details] Patch rs=me. Make sure EWS bots are happy.
Comment on attachment 385406 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=385406&action=review > JSTests/stress/osr-exit-with-interpreter-on-stack.js:1 > +//@ requiredOptions('--thresholdForJITAfterWarmUp=10', '--useConcurrentJIT=0') /requiredOptions/requireOptions/ nit: use '--useConcurrentJIT=false' instead. I've been told in the past that though the bool option is able to take an int, using it in official code is a no-no. So, let's just avoid that.
<rdar://problem/55917224>
Created attachment 385416 [details] Patch for landing
Comment on attachment 385406 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=385406&action=review >> JSTests/stress/osr-exit-with-interpreter-on-stack.js:1 >> +//@ requiredOptions('--thresholdForJITAfterWarmUp=10', '--useConcurrentJIT=0') > > /requiredOptions/requireOptions/ > > nit: use '--useConcurrentJIT=false' instead. I've been told in the past that though the bool option is able to take an int, using it in official code is a no-no. So, let's just avoid that. Whoops, fixed. Ehh, we use 0/1 more than true/false currently so I'm gonna stick with 0.
Comment on attachment 385416 [details] Patch for landing Clearing flags on attachment: 385416 Committed r253384: <https://trac.webkit.org/changeset/253384>
All reviewed patches have been landed. Closing bug.