Adding ia32 simd assembler changes.

Adding ia32 simd assembler support.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=https://bugs.chromium.org/p/v8/issues/detail?id=4124
R=titzer@chromium.org
LOG=N

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

[bradnelson, 2016-05-18 07:57:10]

Description was changed from

==========
Adding ia32 simd assembler changes.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=
R=bbudge@chromium.org
==========

to

==========
Adding ia32 simd assembler changes.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=
R=bbudge@chromium.org
==========

[bradnelson, 2016-05-18 07:57:10]

bradnelson@chromium.org changed reviewers:
+ titzer@chromium.org

[bradnelson, 2016-05-18 08:01:06]

Not really for review yet as I want to do a cleanup pass and check the encodings
myself. But I wanted to carve this out so we can talk about how the assembler
parts of simd should look.

Ben would landing asm changes for ia32/x64/arm based on the intel patch a
reasonable incremental step?

Is just testing disassemble sufficient? I don't see execution tests with the
assemblers, or have I missed them?

[bradnelson, 2016-05-18 08:01:37]

bradnelson@chromium.org changed reviewers:
+ aseemgarg@chromium.org, gdeepti@chromium.org

[titzer, 2016-05-18 09:52:46]

On 2016/05/18 08:01:44, bradnelson wrote:

lgtm other than small comments

[bradnelson, 2016-05-19 07:33:14]

Description was changed from

==========
Adding ia32 simd assembler changes.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=
R=bbudge@chromium.org
==========

to

==========
Adding ia32 simd assembler support.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=https://bugs.chromium.org/p/v8/issues/detail?id=4124
R=titzer@chromium.org
==========

[bradnelson, 2016-05-19 07:33:37]

Description was changed from

==========
Adding ia32 simd assembler support.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=https://bugs.chromium.org/p/v8/issues/detail?id=4124
R=titzer@chromium.org
==========

to

==========
Adding ia32 simd assembler support.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=https://bugs.chromium.org/p/v8/issues/detail?id=4124
R=titzer@chromium.org
LOG=N
==========

[bradnelson, 2016-05-19 07:37:36]

The CQ bit was checked by bradnelson@chromium.org

[bradnelson, 2016-05-19 07:37:37]

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

[commit-bot: I haz the power, 2016-05-19 07:37:46]

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

[commit-bot: I haz the power, 2016-05-19 08:03:08]

Description was changed from

==========
Adding ia32 simd assembler support.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=https://bugs.chromium.org/p/v8/issues/detail?id=4124
R=titzer@chromium.org
LOG=N
==========

to

==========
Adding ia32 simd assembler support.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=https://bugs.chromium.org/p/v8/issues/detail?id=4124
R=titzer@chromium.org
LOG=N
==========

[commit-bot: I haz the power, 2016-05-19 08:03:09]

Committed patchset #2 (id:20001)

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

Description was changed from

==========
Adding ia32 simd assembler support.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=https://bugs.chromium.org/p/v8/issues/detail?id=4124
R=titzer@chromium.org
LOG=N
==========

to

==========
Adding ia32 simd assembler support.

Based on assembler changes from this patch:
https://codereview.chromium.org/90643003/

BUG=https://bugs.chromium.org/p/v8/issues/detail?id=4124
R=titzer@chromium.org
LOG=N

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

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

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

[Michael Achenbach, 2016-05-19 08:57:44]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/1992163002/ by machenbach@chromium.org.

The reason for reverting is: Crashes on win32 debug:
https://build.chromium.org/p/client.v8/builders/V8%20Win32%20-%20debug/builds...

Also, would be nice if the test output could be a bit shorter and only print
what's necessary to trace a failure. Or split things into more smaller tests.
Like that, these logs must be processed, json-encoded/decoded and sent around
through the infrastructure.

Some chars in the output make the json encoder unhappy, therefore the
infrastructure can't nicely display the failures..