Treat HArgumentsObject as a safe use during Uint32 analysis phase.

Treat HArgumentsObject as a safe use during Uint32 analysis phase.

Deoptimization infrastructure already handles it correctly.

This change fixes repetitive deoptimizations in the code like this:

    var u32 = new Uint32Array(1);
    u32[0] = -1;

    function tr(x) { return x|0; }
    function ld() { return tr(u32[0]); }

    while (true) ld();

Currently inlined tr will contain HArgumentsObject that is considered uint32-unsafe use and prevents u32[0] from becoming uint32 load - instead a speculative int32 load is generated which just deopts.

BUG=

Committed: https://crrev.com/021f738127406ef6ff8868465ff32b59edaff016
Cr-Commit-Position: refs/heads/master@{#27781}

[Vyacheslav Egorov (Google), 2015-04-10 12:03:31]

vegorov@google.com changed reviewers:
+ jkummerow@chromium.org, mstarzinger@chromium.org

[Vyacheslav Egorov (Google), 2015-04-10 12:04:00]

Hi Jakob & Michael!

Here is a blast from the past. 

Could you take a look?

[Jakob Kummerow, 2015-04-10 12:15:25]

LGTM.

[Vyacheslav Egorov (Google), 2015-04-13 10:24:56]

The CQ bit was checked by vegorov@google.com

[commit-bot: I haz the power, 2015-04-13 10:25:00]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1077113002/20001

[commit-bot: I haz the power, 2015-04-13 10:47:24]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-04-13 10:47:38]

Patchset 2 (id:??) landed as
https://crrev.com/021f738127406ef6ff8868465ff32b59edaff016
Cr-Commit-Position: refs/heads/master@{#27781}