Try to switch Array builtins into strict mode.

Try to switch Array builtins into strict mode.

R=rossberg@chromium.org
TEST=mjsunit,test262,webkit

Committed: https://code.google.com/p/v8/source/detail?r=20717

[Michael Starzinger, 2014-04-10 13:40:57]

As discussed offline: This is the experiment of switching our Array builtins
into strict mode. That would be in sync with many other builtin JS files that
already are in strict mode. The following behavior changing effects should be
considered:

1) All calls to [[Put]] and friends within those functions now properly throw
(this fixes conformance problems).

2) Higher-order functions no longer appear as the "caller" of callback functions
(the spec is neutral, this is in sync with e.g. FF).
  function cmp() { assertEquals(null, cmp.caller) }
  [1,2,3].sort(cmp)

3) The builtin functions now have a fully poisoned "caller" property, as opposed
to a semi-poisoned that returns "null" instead (the spec is neutral, this
diverges from e.g. FF).
  function cmp() { assertThrows("Array.prototype.sort.caller") }
  [1,2,3].sort(cmp)

4) The above (2) and (3) also apply to the "callee" and "arguments" property.

https://codereview.chromium.org/233083003/diff/1/test/mjsunit/regress/regress...
File test/mjsunit/regress/regress-1548.js (right):

https://codereview.chromium.org/233083003/diff/1/test/mjsunit/regress/regress...
test/mjsunit/regress/regress-1548.js:33: assertThrows(function() { testfn(foo);
} );
These four are the changes that scare me. They reflect the behavioral change (3)
mentioned in my description.

[rossberg, 2014-04-10 14:18:58]

lgtm

[Michael Starzinger, 2014-04-14 11:26:11]

Committed patchset #1 manually as r20717 (presubmit successful).