[turbofan] Robust node caching for relocatable int{32|64}

[turbofan] Robust node caching for relocatable int{32|64}

We should use both the int value as well as the reloc info mode for the
key of a relocatable int{32|64}.

BUG=

Committed: https://crrev.com/c0c3a23101d0d0f4ceacef0399f84b23de3bb857
Cr-Commit-Position: refs/heads/master@{#36762}

[Mircea Trofin, 2016-06-04 05:01:59]

Description was changed from

==========
[turbofan] Robust node caching for relocatable int{32|64}

We should use both the int value as well as the reloc info mode for the
key of a relocatable int{32|64}.

BUG=
==========

to

==========
[turbofan] Robust node caching for relocatable int{32|64}

We should use both the int value as well as the reloc info mode for the
key of a relocatable int{32|64}. 

BUG=
==========

[Mircea Trofin, 2016-06-04 05:02:00]

mtrofin@chromium.org changed reviewers:
+ gdeepti@chromium.org

[Mircea Trofin, 2016-06-04 05:13:29]

I hit this when trying to tease out wasm imports as well as direct 
function calls. For both, I want to first compile the call sites using a 
relocation that stores the index (an int). What differentiates direct
functions from imports is the reloc mode. That was being elided before,
as the cache would remember the first encountered int, regardless of
mode.

[gdeepti, 2016-06-06 15:47:25]

gdeepti@chromium.org changed reviewers:
+ titzer@chromium.org

[gdeepti, 2016-06-06 15:47:25]

lgtm, +titzer

These were only used for wasm memory references so I did not see the need for
increasing the node cache size at that time, agreed that using relocatable
pointers with other relocation modes needs caching to be more robust.

[titzer, 2016-06-06 15:58:30]

lgtm

[Mircea Trofin, 2016-06-06 16:20:13]

The CQ bit was checked by mtrofin@chromium.org

[commit-bot: I haz the power, 2016-06-06 16:20:19]

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

[commit-bot: I haz the power, 2016-06-06 16:45:29]

Description was changed from

==========
[turbofan] Robust node caching for relocatable int{32|64}

We should use both the int value as well as the reloc info mode for the
key of a relocatable int{32|64}. 

BUG=
==========

to

==========
[turbofan] Robust node caching for relocatable int{32|64}

We should use both the int value as well as the reloc info mode for the
key of a relocatable int{32|64}. 

BUG=
==========

[commit-bot: I haz the power, 2016-06-06 16:45:30]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-06 16:47:04]

Description was changed from

==========
[turbofan] Robust node caching for relocatable int{32|64}

We should use both the int value as well as the reloc info mode for the
key of a relocatable int{32|64}. 

BUG=
==========

to

==========
[turbofan] Robust node caching for relocatable int{32|64}

We should use both the int value as well as the reloc info mode for the
key of a relocatable int{32|64}.

BUG=

Committed: https://crrev.com/c0c3a23101d0d0f4ceacef0399f84b23de3bb857
Cr-Commit-Position: refs/heads/master@{#36762}
==========

[commit-bot: I haz the power, 2016-06-06 16:47:05]

Patchset 1 (id:??) landed as
https://crrev.com/c0c3a23101d0d0f4ceacef0399f84b23de3bb857
Cr-Commit-Position: refs/heads/master@{#36762}