[interpreter] Workaround for unused frame states.

[interpreter] Workaround for unused frame states.

This is a temporary workaround for bytecodes which are not guaranteed
to actually use the frame states being created for them. One example
for this are runtime calls to intrinsics, or to runtime functions for
which the frame state count is zero in Linkage::FrameStateInputCount.

This will eventually be reworked into a more generic mechanism that
attaches frame states in the BytecodeGraphBuilder::VisitBytecodes
iteration method itself, instead of in the individual visitors.

R=jarin@chromium.org

Committed: https://crrev.com/3c8edd316f97f2e7ca9b52ed5c38d457b3950eed
Cr-Commit-Position: refs/heads/master@{#33836}

[Michael Starzinger, 2016-02-08 16:49:35]

Description was changed from

==========
[interpreter] Workaround for unused frame states.

This is a temporary workaround for bytecodes which are not guaranteed
to actually used the frame states being created for them. One example
for this are runtime calls to intrinsics, or to runtime functions for
which the frame state count is zero in Linkage::FrameStateInputCount.

This will eventually be reworked into a more generic mechanism that
attaches frame states in the BytecodeGraphBuilder::VisitBytecodes
iteration method itself, instead of in the individual visitors.

R=jarin@chromium.org
==========

to

==========
[interpreter] Workaround for unused frame states.

This is a temporary workaround for bytecodes which are not guaranteed
to actually use the frame states being created for them. One example
for this are runtime calls to intrinsics, or to runtime functions for
which the frame state count is zero in Linkage::FrameStateInputCount.

This will eventually be reworked into a more generic mechanism that
attaches frame states in the BytecodeGraphBuilder::VisitBytecodes
iteration method itself, instead of in the individual visitors.

R=jarin@chromium.org
==========

[Jarin, 2016-02-09 07:04:14]

lgtm. Thanks for helping me with this.

[Michael Starzinger, 2016-02-09 08:25:33]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2016-02-09 08:25:46]

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

[commit-bot: I haz the power, 2016-02-09 08:40:52]

Description was changed from

==========
[interpreter] Workaround for unused frame states.

This is a temporary workaround for bytecodes which are not guaranteed
to actually use the frame states being created for them. One example
for this are runtime calls to intrinsics, or to runtime functions for
which the frame state count is zero in Linkage::FrameStateInputCount.

This will eventually be reworked into a more generic mechanism that
attaches frame states in the BytecodeGraphBuilder::VisitBytecodes
iteration method itself, instead of in the individual visitors.

R=jarin@chromium.org
==========

to

==========
[interpreter] Workaround for unused frame states.

This is a temporary workaround for bytecodes which are not guaranteed
to actually use the frame states being created for them. One example
for this are runtime calls to intrinsics, or to runtime functions for
which the frame state count is zero in Linkage::FrameStateInputCount.

This will eventually be reworked into a more generic mechanism that
attaches frame states in the BytecodeGraphBuilder::VisitBytecodes
iteration method itself, instead of in the individual visitors.

R=jarin@chromium.org
==========

[commit-bot: I haz the power, 2016-02-09 08:40:53]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-09 08:41:29]

Description was changed from

==========
[interpreter] Workaround for unused frame states.

This is a temporary workaround for bytecodes which are not guaranteed
to actually use the frame states being created for them. One example
for this are runtime calls to intrinsics, or to runtime functions for
which the frame state count is zero in Linkage::FrameStateInputCount.

This will eventually be reworked into a more generic mechanism that
attaches frame states in the BytecodeGraphBuilder::VisitBytecodes
iteration method itself, instead of in the individual visitors.

R=jarin@chromium.org
==========

to

==========
[interpreter] Workaround for unused frame states.

This is a temporary workaround for bytecodes which are not guaranteed
to actually use the frame states being created for them. One example
for this are runtime calls to intrinsics, or to runtime functions for
which the frame state count is zero in Linkage::FrameStateInputCount.

This will eventually be reworked into a more generic mechanism that
attaches frame states in the BytecodeGraphBuilder::VisitBytecodes
iteration method itself, instead of in the individual visitors.

R=jarin@chromium.org

Committed: https://crrev.com/3c8edd316f97f2e7ca9b52ed5c38d457b3950eed
Cr-Commit-Position: refs/heads/master@{#33836}
==========

[commit-bot: I haz the power, 2016-02-09 08:41:30]

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