Introduce "optimized_out" oddball marker for compilers.

Introduce "optimized_out" oddball marker for compilers.

This introduces {optimized_out} as another Oddball kind to be used by
optimizing compilers when values are being optimized away. The aim is
providing visibility when this value leaks into the application domain.
Currently this will lead to {undefined} values appearing which then
silently propagate through the application. The special oddball can be
identified easily as a bug and also the debugger can treat it specially
when needed.

R=jarin@chromium.org

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

[Michael Starzinger, 2016-03-16 10:18:43]

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

[Michael Starzinger, 2016-03-16 10:18:44]

Jaro: PTAL.
Jakob: FYI.
Yang: FYI for potential debugger interaction.

[Jarin, 2016-03-16 10:32:13]

lgtm (once the test expectations are fixed).

[Yang, 2016-03-16 12:49:29]

On 2016/03/16 10:32:13, Jarin wrote:
> lgtm (once the test expectations are fixed).

Nice!

[Yang, 2016-03-16 14:23:27]

On 2016/03/16 12:49:29, Yang wrote:
> On 2016/03/16 10:32:13, Jarin wrote:
> > lgtm (once the test expectations are fixed).
> 
> Nice!

lgtm. thanks

[Michael Starzinger, 2016-03-16 14:23:50]

The CQ bit was checked by mstarzinger@chromium.org

[Michael Starzinger, 2016-03-16 14:23:50]

The patchset sent to the CQ was uploaded after l-g-t-m from jarin@chromium.org
Link to the patchset: https://codereview.chromium.org/1810483002/#ps20001
(title: "Fix debugger.")

[commit-bot: I haz the power, 2016-03-16 14:23:57]

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

[commit-bot: I haz the power, 2016-03-16 14:30:23]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-03-16 14:31:06]

Description was changed from

==========
Introduce "optimized_out" oddball marker for compilers.

This introduces {optimized_out} as another Oddball kind to be used by
optimizing compilers when values are being optimized away. The aim is
providing visibility when this value leaks into the application domain.
Currently this will lead to {undefined} values appearing which then
silently propagate through the application. The special oddball can be
identified easily as a bug and also the debugger can treat it specially
when needed.

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

to

==========
Introduce "optimized_out" oddball marker for compilers.

This introduces {optimized_out} as another Oddball kind to be used by
optimizing compilers when values are being optimized away. The aim is
providing visibility when this value leaks into the application domain.
Currently this will lead to {undefined} values appearing which then
silently propagate through the application. The special oddball can be
identified easily as a bug and also the debugger can treat it specially
when needed.

R=jarin@chromium.org

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

[commit-bot: I haz the power, 2016-03-16 14:31:07]

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