[turbofan] Checking monotonicity of representation inference outputs and inputs.

[turbofan] Checking monotonicity of representation inference outputs and inputs.

Monotonicity is not required at the current setup, where we do backward pass through
the graph.  However, for bidirectinal analysis, we'd better be sure that all the
input/use information is monotone.

The checker here is quite strict - it requires monotonicity in each of: use
representations, use truncation, output representation and output type. In future, we can
lower the requirements and use lexicographic ordering (e.g., on use truncation and
representation).

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

[Jarin, 2015-11-30 07:55:10]

Description was changed from

==========
[turbofan] Checking monotonicity of representation inference outputs and inputs.

Monotonicity is not required at the current setup, where we do backward pass
through
the graph.  However, for bidirectinal analysis, we'd better be sure that all the
input/use information is monotone.
==========

to

==========
[turbofan] Checking monotonicity of representation inference outputs and inputs.

Monotonicity is not required at the current setup, where we do backward pass
through
the graph.  However, for bidirectinal analysis, we'd better be sure that all the
input/use information is monotone.

The checker here is quite strict - it requires monotonicity in each of: use
representations, use truncation, output representation and output type. In
future, we can lower the requirements and use lexicographic ordering (e.g., on
use truncation and representation).
==========

[Jarin, 2015-11-30 07:55:10]

jarin@chromium.org changed reviewers:
+ bmeurer@chromium.org

[Jarin, 2015-11-30 07:55:35]

Description was changed from

==========
[turbofan] Checking monotonicity of representation inference outputs and inputs.

Monotonicity is not required at the current setup, where we do backward pass
through
the graph.  However, for bidirectinal analysis, we'd better be sure that all the
input/use information is monotone.

The checker here is quite strict - it requires monotonicity in each of: use
representations, use truncation, output representation and output type. In
future, we can lower the requirements and use lexicographic ordering (e.g., on
use truncation and representation).
==========

to

==========
[turbofan] Checking monotonicity of representation inference outputs and inputs.

Monotonicity is not required at the current setup, where we do backward pass
through
the graph.  However, for bidirectinal analysis, we'd better be sure that all the
input/use information is monotone.

The checker here is quite strict - it requires monotonicity in each of: use 
representations, use truncation, output representation and output type. In
future, we can 
lower the requirements and use lexicographic ordering (e.g., on use truncation
and 
representation).
==========

[Jarin, 2015-11-30 07:56:11]

Could you take a look, please?

[Benedikt Meurer, 2015-11-30 08:34:03]

Nice. LGTM.

[Jarin, 2015-11-30 09:15:27]

The CQ bit was checked by jarin@chromium.org

[commit-bot: I haz the power, 2015-11-30 09:15:38]

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

[commit-bot: I haz the power, 2015-11-30 09:22:25]

Description was changed from

==========
[turbofan] Checking monotonicity of representation inference outputs and inputs.

Monotonicity is not required at the current setup, where we do backward pass
through
the graph.  However, for bidirectinal analysis, we'd better be sure that all the
input/use information is monotone.

The checker here is quite strict - it requires monotonicity in each of: use 
representations, use truncation, output representation and output type. In
future, we can 
lower the requirements and use lexicographic ordering (e.g., on use truncation
and 
representation).
==========

to

==========
[turbofan] Checking monotonicity of representation inference outputs and inputs.

Monotonicity is not required at the current setup, where we do backward pass
through
the graph.  However, for bidirectinal analysis, we'd better be sure that all the
input/use information is monotone.

The checker here is quite strict - it requires monotonicity in each of: use 
representations, use truncation, output representation and output type. In
future, we can 
lower the requirements and use lexicographic ordering (e.g., on use truncation
and 
representation).
==========

[commit-bot: I haz the power, 2015-11-30 09:22:25]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-11-30 09:22:46]

Description was changed from

==========
[turbofan] Checking monotonicity of representation inference outputs and inputs.

Monotonicity is not required at the current setup, where we do backward pass
through
the graph.  However, for bidirectinal analysis, we'd better be sure that all the
input/use information is monotone.

The checker here is quite strict - it requires monotonicity in each of: use 
representations, use truncation, output representation and output type. In
future, we can 
lower the requirements and use lexicographic ordering (e.g., on use truncation
and 
representation).
==========

to

==========
[turbofan] Checking monotonicity of representation inference outputs and inputs.

Monotonicity is not required at the current setup, where we do backward pass
through
the graph.  However, for bidirectinal analysis, we'd better be sure that all the
input/use information is monotone.

The checker here is quite strict - it requires monotonicity in each of: use
representations, use truncation, output representation and output type. In
future, we can
lower the requirements and use lexicographic ordering (e.g., on use truncation
and
representation).

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

[commit-bot: I haz the power, 2015-11-30 09:22:47]

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