PPC/s390: [Turbofan]: Use new MachineTypes in access-builder.

PPC/s390: [Turbofan]: Use new MachineTypes in access-builder.

Port 56429fc14671a10749190a4dfeacd38b7270f6f5

Original Commit Message:

    Introduced MachineType::TaggedSigned() and TaggedPointer().

    The idea is to quit using the representational dimension of Type, and
    instead encode this information in the MachineRepresentation (itself
    lightly wrapped in MachineType, along with MachineSemantic).

    There are three parts to the whole change:

    1) Places that set the machine representation - constant nodes, loads nad
       stores, global object and native context specialization.

    2) Places that propagate type/representation - this is representation
       inference (aka simplified lowering). At the end of this process we
       expect to have a MachineRepresentation for every node. An interesting
       part of this is phi merging.

    3) Places that examine representation - WriteBarrier elimination does this.
       Currently it's looking at the Type representation dimension, but as
       a part of this change (or in a soon-to-follow change) it can simply
       examine the MachineRepresentation.

R=mvstanton@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
BUG=
LOG=N

Review-Url: https://codereview.chromium.org/2662223003
Cr-Commit-Position: refs/heads/master@{#42817}
Committed: https://chromium.googlesource.com/v8/v8/+/7c982e7ecf7669c05af199bf827dd80110f37cad

[JaideepBajwa, 2017-01-31 15:15:59]

ptal

[john.yan, 2017-01-31 15:16:43]

lgtm

[JaideepBajwa, 2017-01-31 15:17:02]

The CQ bit was checked by bjaideep@ca.ibm.com

[commit-bot: I haz the power, 2017-01-31 15:17:12]

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, 2017-01-31 15:40:27]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1485875822361420, "parent_rev":
"9cf7cb4c6784372e5820049cf91423c9b58d15e1", "commit_rev":
"7c982e7ecf7669c05af199bf827dd80110f37cad"}

[commit-bot: I haz the power, 2017-01-31 15:40:31]

Description was changed from

==========
PPC/s390: [Turbofan]: Use new MachineTypes in access-builder.

Port 56429fc14671a10749190a4dfeacd38b7270f6f5

Original Commit Message:

    Introduced MachineType::TaggedSigned() and TaggedPointer().

    The idea is to quit using the representational dimension of Type, and
    instead encode this information in the MachineRepresentation (itself
    lightly wrapped in MachineType, along with MachineSemantic).

    There are three parts to the whole change:

    1) Places that set the machine representation - constant nodes, loads nad
       stores, global object and native context specialization.

    2) Places that propagate type/representation - this is representation
       inference (aka simplified lowering). At the end of this process we
       expect to have a MachineRepresentation for every node. An interesting
       part of this is phi merging.

    3) Places that examine representation - WriteBarrier elimination does this.
       Currently it's looking at the Type representation dimension, but as
       a part of this change (or in a soon-to-follow change) it can simply
       examine the MachineRepresentation.

R=mvstanton@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=
LOG=N
==========

to

==========
PPC/s390: [Turbofan]: Use new MachineTypes in access-builder.

Port 56429fc14671a10749190a4dfeacd38b7270f6f5

Original Commit Message:

    Introduced MachineType::TaggedSigned() and TaggedPointer().

    The idea is to quit using the representational dimension of Type, and
    instead encode this information in the MachineRepresentation (itself
    lightly wrapped in MachineType, along with MachineSemantic).

    There are three parts to the whole change:

    1) Places that set the machine representation - constant nodes, loads nad
       stores, global object and native context specialization.

    2) Places that propagate type/representation - this is representation
       inference (aka simplified lowering). At the end of this process we
       expect to have a MachineRepresentation for every node. An interesting
       part of this is phi merging.

    3) Places that examine representation - WriteBarrier elimination does this.
       Currently it's looking at the Type representation dimension, but as
       a part of this change (or in a soon-to-follow change) it can simply
       examine the MachineRepresentation.

R=mvstanton@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=
LOG=N

Review-Url: https://codereview.chromium.org/2662223003
Cr-Commit-Position: refs/heads/master@{#42817}
Committed:
https://chromium.googlesource.com/v8/v8/+/7c982e7ecf7669c05af199bf827dd80110f...
==========

[commit-bot: I haz the power, 2017-01-31 15:40:32]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/7c982e7ecf7669c05af199bf827dd80110f...