Update GN build files with the cpu_arch -> current_cpu change.

Update GN build files with the cpu_arch -> current_cpu change.

R=machenbach@chromium.org, jochen@chromium.org
BUG=crbug.com/344767
LOG=Y

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

[Dirk Pranke, 2015-02-20 20:56:51]

dpranke@chromium.org changed reviewers:
+ jochen@chromium.org

[Michael Achenbach, 2015-02-21 21:07:09]

lgtm

[jochen (gone - plz use gerrit), 2015-02-23 07:49:19]

https://codereview.chromium.org/946023002/diff/20001/BUILD.gn
File BUILD.gn (right):

https://codereview.chromium.org/946023002/diff/20001/BUILD.gn#newcode21
BUILD.gn:21: v8_target_arch = current_cpu
is current_cpu always the target arch? i.e. is it for cross compiling from ia32
to arm always "arm" in both the host and target toolchain?

[Dirk Pranke, 2015-02-23 18:58:16]

https://codereview.chromium.org/946023002/diff/20001/BUILD.gn
File BUILD.gn (right):

https://codereview.chromium.org/946023002/diff/20001/BUILD.gn#newcode21
BUILD.gn:21: v8_target_arch = current_cpu
On 2015/02/23 07:49:19, jochen (slow) wrote:
> is current_cpu always the target arch? i.e. is it for cross compiling from
ia32
> to arm always "arm" in both the host and target toolchain?

No. This change is actually "wrong" in that it preserves what v8 was doing
before my cpu_arch -> current_cpu change.

The right thing to do is to use the new 'target_cpu' variable, which will always
be the "arm" you want, above. Doing so probably also will allow us to get rid of
"v8_target_arch".

However, I want to make those changes in a separate CL to avoid any confusion;
this CL should have no semantic changes.

[Dirk Pranke, 2015-02-23 20:21:24]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2015-02-23 20:22:16]

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

[commit-bot: I haz the power, 2015-02-23 20:27:36]

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

[commit-bot: I haz the power, 2015-02-23 20:27:37]

Try jobs failed on following builders:
  v8_presubmit on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_presubmit/builds/761)

[Dirk Pranke, 2015-02-23 20:29:37]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2015-02-23 20:30:16]

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

[commit-bot: I haz the power, 2015-02-23 21:01:37]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-02-23 21:01:39]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-02-23 21:01:48]

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