Check the state of the current binary op IC before patching smi code

Check the state of the current binary op IC before patching smi code

Between the miss and patching, we run user code. That may already patch the same code. IC refactoring broke this (again), so including a regression test this time around.

BUG=chromium:601392
LOG=n

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

[Toon Verwaest, 2016-04-27 08:15:32]

verwaest@chromium.org changed reviewers:
+ ishell@chromium.org

[Toon Verwaest, 2016-04-27 08:15:33]

ptal

[Igor Sheludko, 2016-04-27 08:48:28]

lgtm

[Toon Verwaest, 2016-04-27 08:51:15]

The CQ bit was checked by verwaest@chromium.org

[commit-bot: I haz the power, 2016-04-27 08:51:23]

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

[commit-bot: I haz the power, 2016-04-27 09:16:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-27 09:19:20]

Description was changed from

==========
Check the state of the current binary op IC before patching smi code

Between the miss and patching, we run user code. That may already patch the same
code. IC refactoring broke this (again), so including a regression test this
time around.

BUG=chromium:601392
LOG=n
==========

to

==========
Check the state of the current binary op IC before patching smi code

Between the miss and patching, we run user code. That may already patch the same
code. IC refactoring broke this (again), so including a regression test this
time around.

BUG=chromium:601392
LOG=n

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

[commit-bot: I haz the power, 2016-04-27 09:19:21]

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