WIP: Boom

WIP: Boom
#
# Fatal error in ../src/compiler/code-assembler.cc, line 677
# Check failed: i != variable_merges_.end() && i->second.size() == merge_count_.
#

This can be "fixed" by moving {var_boom} declaration to the outermost scope and binding it to some value. I'm not sure if it really has to be this way.

Another way is to introduce a {return_true_trampoline} block and jump to {return_true} through it (see Patch Set 2).

BUG=chromium:615621

[Igor Sheludko, 2016-05-13 10:58:55]

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

[Igor Sheludko, 2016-05-13 10:58:55]

PTAL

[Igor Sheludko, 2016-05-20 09:01:18]

Description was changed from

==========
WIP: Boom

Fatal error in ../src/compiler/code-assembler.cc, line 677
Check failed: i != variable_merges_.end() && i->second.size() == merge_count_.
==========

to

==========
WIP: Boom

Fatal error in ../src/compiler/code-assembler.cc, line 677
Check failed: i != variable_merges_.end() && i->second.size() == merge_count_.


This can be "fixed" by moving {var_boom} declaration to the outermost scope and
binding it to some value. I'm not sure if it really has to be this way.
==========

[Igor Sheludko, 2016-05-20 09:01:29]

On 2016/05/13 10:58:55, Igor Sheludko wrote:
> PTAL

This can be "fixed" by moving {var_boom} declaration to the outermost scope and
binding it to some value. I'm not sure if it really has to be this way.

[Igor Sheludko, 2016-05-28 12:52:51]

Description was changed from

==========
WIP: Boom

Fatal error in ../src/compiler/code-assembler.cc, line 677
Check failed: i != variable_merges_.end() && i->second.size() == merge_count_.


This can be "fixed" by moving {var_boom} declaration to the outermost scope and
binding it to some value. I'm not sure if it really has to be this way.
==========

to

==========
WIP: Boom
#
# Fatal error in ../src/compiler/code-assembler.cc, line 677
# Check failed: i != variable_merges_.end() && i->second.size() == merge_count_.
#


This can be "fixed" by moving {var_boom} declaration to the outermost scope and
binding it to some value. I'm not sure if it really has to be this way.

Another way is to introduce a {return_true_trampoline} block and jump to
{return_true} through it (see PatchSet2).

BUG=chromium:615621
==========

[Igor Sheludko, 2016-05-28 12:53:02]

Description was changed from

==========
WIP: Boom
#
# Fatal error in ../src/compiler/code-assembler.cc, line 677
# Check failed: i != variable_merges_.end() && i->second.size() == merge_count_.
#


This can be "fixed" by moving {var_boom} declaration to the outermost scope and
binding it to some value. I'm not sure if it really has to be this way.

Another way is to introduce a {return_true_trampoline} block and jump to
{return_true} through it (see PatchSet2).

BUG=chromium:615621
==========

to

==========
WIP: Boom
#
# Fatal error in ../src/compiler/code-assembler.cc, line 677
# Check failed: i != variable_merges_.end() && i->second.size() == merge_count_.
#

This can be "fixed" by moving {var_boom} declaration to the outermost scope and
binding it to some value. I'm not sure if it really has to be this way.

Another way is to introduce a {return_true_trampoline} block and jump to
{return_true} through it (see PatchSet2).

BUG=chromium:615621
==========

[Igor Sheludko, 2016-05-28 12:53:37]

On 2016/05/20 09:01:29, Igor Sheludko wrote:
> On 2016/05/13 10:58:55, Igor Sheludko wrote:
> > PTAL
> 
> This can be "fixed" by moving {var_boom} declaration to the outermost scope
and
> binding it to some value. I'm not sure if it really has to be this way.

Another workaround is shown in Patch Set 2.

[Igor Sheludko, 2016-05-28 12:53:59]

Description was changed from

==========
WIP: Boom
#
# Fatal error in ../src/compiler/code-assembler.cc, line 677
# Check failed: i != variable_merges_.end() && i->second.size() == merge_count_.
#

This can be "fixed" by moving {var_boom} declaration to the outermost scope and
binding it to some value. I'm not sure if it really has to be this way.

Another way is to introduce a {return_true_trampoline} block and jump to
{return_true} through it (see PatchSet2).

BUG=chromium:615621
==========

to

==========
WIP: Boom
#
# Fatal error in ../src/compiler/code-assembler.cc, line 677
# Check failed: i != variable_merges_.end() && i->second.size() == merge_count_.
#

This can be "fixed" by moving {var_boom} declaration to the outermost scope and
binding it to some value. I'm not sure if it really has to be this way.

Another way is to introduce a {return_true_trampoline} block and jump to
{return_true} through it (see Patch Set 2).

BUG=chromium:615621
==========

[Igor Sheludko, 2016-05-30 13:01:03]

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

[Igor Sheludko, 2016-05-30 13:01:04]

I rebased the CL. 
Define ENABLE_TRAMPOLINE_WORKAROUND to 1 to enable the workaround.