Improve optimization of operations on indexables by using more inferred type information and by dis…

tests/html/html.status

Index: tests/html/html.status
diff --git a/tests/html/html.status b/tests/html/html.status
index 9b942d150238bedb0ba1244600b5534ce24137f6..111a56a412fee561b76e8581f1b0818bd8ef427a 100644
--- a/tests/html/html.status
+++ b/tests/html/html.status
@@ -19,9 +19,6 @@ worker_test/functional: Pass, Crash # Issue 9929.
 [ $compiler == dart2js && ($runtime == ie9 || $runtime == ie10 || $runtime == safari || $runtime == ff || $runtime == chrome || $runtime == opera || $runtime == drt || $runtime == dartium)]
 dom_isolates_test: Skip # Need to migrate to new spawnDomFunction.
 
-[ $compiler == dart2js && ($runtime == ie10 || $runtime == safari || $runtime == ff || $runtime == chrome || $runtime == opera || $runtime == drt || $runtime == dartium)]
-typed_arrays_range_checks_test: Fail # TODO(vsm): Implement range checks.

[vsm, 2013/04/25 00:07:08]

Kasper - I was just looking into adding explicit bounds checks here.  Are they
no longer needed?  Looks like you're special casing the typed lists now.

[kasperl, 2013/04/25 05:24:31]

There's still more to do. What I added in this CL gives us index bounds checks
for typed data lists whenever we optimize the access to them -- if we have too
little type information available to us to optimize the access, we will still
call the [] and []= operators on the typed lists.

It's a little bit weird, but we now have index checks in the optimized case -
and no such checks in the unoptimized case.

-
 [ $compiler == dart2js && $runtime == ie10 ]
 indexeddb_3_test: Pass, Timeout, Slow # Issue: http://dartbug.com/9437
 indexeddb_4_test: Pass, Timeout, Slow # Issue: http://dartbug.com/9437