Remove catch prediction from handler table API.

Remove catch prediction from handler table API.

This removes the ability to specify a catch prediction for exception
handler tables that are based on return addresses. The encoding for
handlers still looks the same to keep it in sync with tables based on
ranges, just no payload is stored in the respective bits.

R=yangguo@chromium.org

Committed: https://crrev.com/13d2feefbaa293cf7e32126129ec1fa284b50b4a
Cr-Commit-Position: refs/heads/master@{#38327}

[Michael Starzinger, 2016-08-02 14:53:34]

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

[commit-bot: I haz the power, 2016-08-02 14:53:40]

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

[Michael Starzinger, 2016-08-02 15:00:24]

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

[commit-bot: I haz the power, 2016-08-02 15:00:32]

Dry run: 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-08-02 15:42:29]

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

[commit-bot: I haz the power, 2016-08-02 15:42:29]

Dry run: This issue passed the CQ dry run.

[Michael Starzinger, 2016-08-02 16:15:04]

Description was changed from

==========
Remove catch prediction from handler table API.

This removes the ability to specify a catch prediction for exception
handler tables that are based onf return addresses. The encoding for
handlers still looks the same to keep it in sync with tables based on
ranges, just no payload is stored in those bits.

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

to

==========
Remove catch prediction from handler table API.

This removes the ability to specify a catch prediction for exception
handler tables that are based on return addresses. The encoding for
handlers still looks the same to keep it in sync with tables based on
ranges, just no payload is stored in the respective bits.

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

[Yang, 2016-08-04 07:28:30]

On 2016/08/02 14:46:24, Michael Starzinger wrote:

lgtm.

[Michael Starzinger, 2016-08-04 07:54:47]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2016-08-04 07:54:53]

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-08-04 08:19:24]

Description was changed from

==========
Remove catch prediction from handler table API.

This removes the ability to specify a catch prediction for exception
handler tables that are based on return addresses. The encoding for
handlers still looks the same to keep it in sync with tables based on
ranges, just no payload is stored in the respective bits.

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

to

==========
Remove catch prediction from handler table API.

This removes the ability to specify a catch prediction for exception
handler tables that are based on return addresses. The encoding for
handlers still looks the same to keep it in sync with tables based on
ranges, just no payload is stored in the respective bits.

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

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

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-08-04 08:22:33]

Description was changed from

==========
Remove catch prediction from handler table API.

This removes the ability to specify a catch prediction for exception
handler tables that are based on return addresses. The encoding for
handlers still looks the same to keep it in sync with tables based on
ranges, just no payload is stored in the respective bits.

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

to

==========
Remove catch prediction from handler table API.

This removes the ability to specify a catch prediction for exception
handler tables that are based on return addresses. The encoding for
handlers still looks the same to keep it in sync with tables based on
ranges, just no payload is stored in the respective bits.

R=yangguo@chromium.org

Committed: https://crrev.com/13d2feefbaa293cf7e32126129ec1fa284b50b4a
Cr-Commit-Position: refs/heads/master@{#38327}
==========

[commit-bot: I haz the power, 2016-08-04 08:22:33]

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