This is a meta bug for optimizations that will help JM do stuff on the web faster. We have to prioritize benchmark wins for the immediate future, so this stuff is strictly lower priority than the bugs hung off JaegerSpeed for now.
Isn't this antithetical to the sentiment in, for example, bug 410460 (that things shouldn't be done just to improve benchmark performance)?
(In reply to comment #1) > Isn't this antithetical to the sentiment in, for example, bug 410460 (that > things shouldn't be done just to improve benchmark performance)? If we are not fast on the JS benchmarks, then too many people will think we are slow. The benchmark wins will help many real programs, too--all the bugs I filed speed up things that people reasonably would do in their JS programs. It's just a matter of what order we do the optimizations in. Once our scores are good we don't have to worry about them so much any more and can focus on cooler things like WebGL Quake.
This kind of giant-scope meta bug is not wanted for K9O.
Is this still for JM or SM too or just IM, or JS in general? If so, please clarify the summary/headline.