[compiler] Remove obsolete guard in MarkForOptimization.

[compiler] Remove obsolete guard in MarkForOptimization.

The guard in JSFunction::MarkForOptimization checking whether a function
is being debugged is overly protective. The compilation pipeline will
bailout itself in that circumstance. Having the runtime behave similar
makes sure the debugger observes a situation closer to reality.

R=yangguo@chromium.org

Committed: https://crrev.com/1705b7de4f22fbd7492c27ccc8fa25348fbc945d
Cr-Commit-Position: refs/heads/master@{#35625}

[titzer, 2016-04-19 13:28:03]

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

[titzer, 2016-04-19 13:28:03]

Drive-by lgtm, as you know I hate asserts :)

[Michael Starzinger, 2016-04-19 13:40:13]

Description was changed from

==========
[compiler] Remove obsolete guard in MarkForOptimization.

The guard in JSFunction::MarkForOptimization checking whether a function
is being debugged is overly protective. The compilation pipeline will
bailout itself in that circumstance. Having the runtime behave similar
makes sure the debugger observes a situation closer to reality.

R=
==========

to

==========
[compiler] Remove obsolete guard in MarkForOptimization.

The guard in JSFunction::MarkForOptimization checking whether a function
is being debugged is overly protective. The compilation pipeline will
bailout itself in that circumstance. Having the runtime behave similar
makes sure the debugger observes a situation closer to reality.

R=yangguo@chromium.org
==========

[Michael Starzinger, 2016-04-19 13:40:13]

mstarzinger@chromium.org changed reviewers:
+ yangguo@chromium.org

[Michael Starzinger, 2016-04-19 13:40:23]

Yang: PTAL.

[Yang, 2016-04-19 14:36:26]

On 2016/04/19 13:40:23, Michael Starzinger wrote:
> Yang: PTAL.

lgtm.

[Michael Starzinger, 2016-04-19 14:39:38]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2016-04-19 14:39:45]

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

[commit-bot: I haz the power, 2016-04-19 14:42:08]

Description was changed from

==========
[compiler] Remove obsolete guard in MarkForOptimization.

The guard in JSFunction::MarkForOptimization checking whether a function
is being debugged is overly protective. The compilation pipeline will
bailout itself in that circumstance. Having the runtime behave similar
makes sure the debugger observes a situation closer to reality.

R=yangguo@chromium.org
==========

to

==========
[compiler] Remove obsolete guard in MarkForOptimization.

The guard in JSFunction::MarkForOptimization checking whether a function
is being debugged is overly protective. The compilation pipeline will
bailout itself in that circumstance. Having the runtime behave similar
makes sure the debugger observes a situation closer to reality.

R=yangguo@chromium.org
==========

[commit-bot: I haz the power, 2016-04-19 14:42:08]

Committed patchset #1 (id:1)

[nodir1, 2016-04-22 18:42:58]

Description was changed from

==========
[compiler] Remove obsolete guard in MarkForOptimization.

The guard in JSFunction::MarkForOptimization checking whether a function
is being debugged is overly protective. The compilation pipeline will
bailout itself in that circumstance. Having the runtime behave similar
makes sure the debugger observes a situation closer to reality.

R=yangguo@chromium.org
==========

to

==========
[compiler] Remove obsolete guard in MarkForOptimization.

The guard in JSFunction::MarkForOptimization checking whether a function
is being debugged is overly protective. The compilation pipeline will
bailout itself in that circumstance. Having the runtime behave similar
makes sure the debugger observes a situation closer to reality.

R=yangguo@chromium.org

Committed: https://crrev.com/1705b7de4f22fbd7492c27ccc8fa25348fbc945d
Cr-Commit-Position: refs/heads/master@{#35625}
==========

[nodir1, 2016-04-22 18:42:59]

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