Comment #2 on issue 3375 by [email protected]: Global legacy const
ignored writable attribute
http://code.google.com/p/v8/issues/detail?id=3375
This is a whole assortment of bugs. First of all, you are right, using
Object.defineProperty triggers the same problem (my bug title might have
been chosen poorly in that regard).
1) Commenting out the f(42) and the f(65) call makes the test pass, because
the IC is not yet monomorphic and hence f(99) will behave correctly.
2) Commenting out the f(65) call will already trigger the bug, because the
IC in the full-codegen version of "f" is borked.
3) Optimizing "f" will actually case the cell access to be completely
inlined into optimized code, which is borked. We will deopt, because an
unrelated hole-check kicks in, but the test still fails.
To sum it up: SNAFU.
--
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.
