On 2015/01/19 12:19:22, Michael Starzinger wrote:
Reason for the change is, that the following two invocation behave
unexpectedly
and surprisingly different:
1) $ d8 --allow-natives-syntax -e "function f() { try {} catch(e) {} }
f();
%OptimizeFunctionOnNextCall(f); f();" --turbo-filter=* --trace-opt
2) $ d8 --allow-natives-syntax -e "function f() { try {} catch(e) {} }
%OptimizeFunctionOnNextCall(f); f();" --turbo-filter=* --trace-opt
Here 1) will not enter the optimizing pipeline, because optimization has
been
disabled on the SharedFunctionInfo already, whereas 2) will enter the
optimizing
pipeline and let the pipeline bailout on it's own. I think the pipeline
should
have the final say in this matter.
Can we make the examples above into some mjsunit tests?
https://codereview.chromium.org/863443003/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
