Comment #4 on issue 3354 by [email protected]: Inlining heuristics still
take source size into account
http://code.google.com/p/v8/issues/detail?id=3354
I see, indeed I can repro somewhat lower scores with
--max_inlined_source_size=800.
It kinda strange that if I say just minify identifiers and remove
whitespace in DeltaBlue without changing any code then it will become a bit
slower.
Maybe inlining heuristics need to be tweaked in some other place to offset
more aggressive inlining? Why does more aggressive inlining lead to worse
scores in the first place?
--
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.
