There's a couple minor bugs in the test which allows variables to leak into the global scope. Please see the attached patch.
Created attachment 19481 [details] string-validate-input.js patch
Created attachment 19482 [details] string-validate-input.js patch
Thanks John, Changes look sane to me, but i'm not sure what the story is with changes to sunspider -- maciej is probably best to look into things like this, but any changes to performance characteristics makes it harder to compare prior results. Then again we already know of a couple of bug fixes which will have to be fixed at some point anyway :-/
Thanks Oliver - that's perfectly understandable. I figure that when it comes time for the next big update a bunch of these fixes can be grouped together; I just wanted to make sure that they don't get forgotten.
Comment on attachment 19482 [details] string-validate-input.js patch Not a bug. This test intentionally testing cases where variables are not declared. This correctly reflects the sloppiness you'll see in lots of real world scripts. Most JavaScript engines are faster if you declare the variables, but this test is testing the slower code path.
Maciej, please correct me if I'm mistaken.
I don't think this test is intentionally testing variables that are not declared. Some of the tests are, but in this case it is not intentional.
Since this doesn't affect correctness of the test output, I think we'll wait to address this in SunSpider 2.0.
See also Bug 60937.