Comment #4 on issue 2741 by [email protected]: max_opt_count is
implemented using the wrong kind of limit
http://code.google.com/p/v8/issues/detail?id=2741
@jkummerow Do you not understand what I'm attempting to say here? Yes, the
--max-opt-count flag works as its designed but the bug is that the amount a
loop should be attempted to optimize shouldn't even be dependant on this
flag.
The amount a function should be optimized should be dependant on it's
length and how often it's even going to be executed since having v8
optimize code it will never see again is what I'm trying to suggest a fix
for which can't be based on a fixed number of times to optimize.
Please think about this :( Since I did give examples where your current
implementation falls short of delivering an intelligent optimization. If
it degrades that should show a fault in concept(the "bug" I'm trying to
raise) not in a buggy implementation. Or maybe am I missing where this
actually happens and I just am unaware of where this can be changed?
--
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/groups/opt_out.
