Comment #3 on issue 4053 by [email protected]: setters-on-elements
test bug.
https://code.google.com/p/v8/issues/detail?id=4053
This part of the test tests specifically that unoptimized code behaves
correctly. Executing foo three times will not optimize it. That's precisely
the assumption that this "assertUnoptimized" guards/documents! The reason
we have "assertUnoptimized" there is because we want to be sure the
scenario you describe ("foo" got optimized unexpectedly) didn't happen.
Are you trying to make the optimizer more aggressive? Don't do that. If
anything, we should be optimizing later, not earlier.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
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.
