gpu, cmaa: avoid == for float in GLSL

gpu, cmaa: avoid == for float in GLSL

According to the GLSL spec, GLSL float can represent exact integers between 0 and 2048.
However, some drivers might not respect the spec. So use uint for == operator.

In detail,
1. GLSL uses IEEE 754 float or half float.
https://www.opengl.org/wiki/Data_Type_(GLSL)#Scalars
2. IEEE 754 half float preserves integers between 0 and 2048 exactly represented.
https://en.wikipedia.org/wiki/Half-precision_floating-point_format#Precision_limitations_on_integer_values

BUG=535198
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

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

[dshwang, 2016-07-21 17:23:16]

Description was changed from

==========
gpu, cmaa: avoid == of float in GLSL

According to the GLSL spec, GLSL float can represent exact integers between 0
and 2048.
However, some drivers might not respect the spec. So use uint for == operator.

In detail,
1. GLSL uses IEEE 754 float or half float.
https://www.opengl.org/wiki/Data_Type_(GLSL)#Scalars
2. IEEE 754 half float preserves integers between 0 and 2048 exactly
represented.
https://en.wikipedia.org/wiki/Half-precision_floating-point_format#Precision_...

BUG=535198
==========

to

==========
gpu, cmaa: avoid == of float in GLSL

According to the GLSL spec, GLSL float can represent exact integers between 0
and 2048.
However, some drivers might not respect the spec. So use uint for == operator.

In detail,
1. GLSL uses IEEE 754 float or half float.
https://www.opengl.org/wiki/Data_Type_(GLSL)#Scalars
2. IEEE 754 half float preserves integers between 0 and 2048 exactly
represented.
https://en.wikipedia.org/wiki/Half-precision_floating-point_format#Precision_...

BUG=535198
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[inactive_dshwang_plz_cc_intel, 2016-07-21 17:23:23]

The CQ bit was checked by dongseong.hwang@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-07-21 17:23:54]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[dshwang, 2016-07-21 17:24:43]

dongseong.hwang@intel.com changed reviewers:
+ piman@chromium.org
- dongseong.hwang@chromium.org

[dshwang, 2016-07-21 17:24:44]

piman@, could you review this simple CL?

[dshwang, 2016-07-21 17:24:59]

Description was changed from

==========
gpu, cmaa: avoid == of float in GLSL

According to the GLSL spec, GLSL float can represent exact integers between 0
and 2048.
However, some drivers might not respect the spec. So use uint for == operator.

In detail,
1. GLSL uses IEEE 754 float or half float.
https://www.opengl.org/wiki/Data_Type_(GLSL)#Scalars
2. IEEE 754 half float preserves integers between 0 and 2048 exactly
represented.
https://en.wikipedia.org/wiki/Half-precision_floating-point_format#Precision_...

BUG=535198
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
gpu, cmaa: avoid == for float in GLSL

According to the GLSL spec, GLSL float can represent exact integers between 0
and 2048.
However, some drivers might not respect the spec. So use uint for == operator.

In detail,
1. GLSL uses IEEE 754 float or half float.
https://www.opengl.org/wiki/Data_Type_(GLSL)#Scalars
2. IEEE 754 half float preserves integers between 0 and 2048 exactly
represented.
https://en.wikipedia.org/wiki/Half-precision_floating-point_format#Precision_...

BUG=535198
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[piman, 2016-07-21 17:32:35]

lgtm

[commit-bot: I haz the power, 2016-07-21 19:41:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-07-21 19:41:21]

Dry run: Try jobs failed on following builders:
  mac_optional_gpu_tests_rel on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_optional_gpu_...)

[dshwang, 2016-07-25 12:55:30]

The CQ bit was checked by dongseong.hwang@intel.com

[commit-bot: I haz the power, 2016-07-25 12:55:41]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-25 13:49:54]

Description was changed from

==========
gpu, cmaa: avoid == for float in GLSL

According to the GLSL spec, GLSL float can represent exact integers between 0
and 2048.
However, some drivers might not respect the spec. So use uint for == operator.

In detail,
1. GLSL uses IEEE 754 float or half float.
https://www.opengl.org/wiki/Data_Type_(GLSL)#Scalars
2. IEEE 754 half float preserves integers between 0 and 2048 exactly
represented.
https://en.wikipedia.org/wiki/Half-precision_floating-point_format#Precision_...

BUG=535198
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
gpu, cmaa: avoid == for float in GLSL

According to the GLSL spec, GLSL float can represent exact integers between 0
and 2048.
However, some drivers might not respect the spec. So use uint for == operator.

In detail,
1. GLSL uses IEEE 754 float or half float.
https://www.opengl.org/wiki/Data_Type_(GLSL)#Scalars
2. IEEE 754 half float preserves integers between 0 and 2048 exactly
represented.
https://en.wikipedia.org/wiki/Half-precision_floating-point_format#Precision_...

BUG=535198
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[commit-bot: I haz the power, 2016-07-25 13:49:55]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-25 13:51:33]

Description was changed from

==========
gpu, cmaa: avoid == for float in GLSL

According to the GLSL spec, GLSL float can represent exact integers between 0
and 2048.
However, some drivers might not respect the spec. So use uint for == operator.

In detail,
1. GLSL uses IEEE 754 float or half float.
https://www.opengl.org/wiki/Data_Type_(GLSL)#Scalars
2. IEEE 754 half float preserves integers between 0 and 2048 exactly
represented.
https://en.wikipedia.org/wiki/Half-precision_floating-point_format#Precision_...

BUG=535198
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
gpu, cmaa: avoid == for float in GLSL

According to the GLSL spec, GLSL float can represent exact integers between 0
and 2048.
However, some drivers might not respect the spec. So use uint for == operator.

In detail,
1. GLSL uses IEEE 754 float or half float.
https://www.opengl.org/wiki/Data_Type_(GLSL)#Scalars
2. IEEE 754 half float preserves integers between 0 and 2048 exactly
represented.
https://en.wikipedia.org/wiki/Half-precision_floating-point_format#Precision_...

BUG=535198
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

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

[commit-bot: I haz the power, 2016-07-25 13:51:34]

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