Rename TARGET_OS_* to HOST_OS_*.

Rename TARGET_OS_* to HOST_OS_*.

Like HOST_ARCH_*, HOST_OS_* describes the OS the VM is running on, which may be different from the OS the VM is generating code for during AOT compilation.

Currently we conflate the two when emitting AOT as assembly, and we get away with it because Flutter only uses assembly for targeting iOS and one can only target iOS from a Mac, but we expect to use assembly for Android as well so native tools can unwind Dart frames.

R=zra@google.com

Committed: https://github.com/dart-lang/sdk/commit/877284947b72bf719bc0defc5d97a6163b3f59e6

[rmacnak, 2017-03-14 22:37:38]

Description was changed from

==========
Rename TARGET_OS_X to HOST_OS_X.

Like HOST_ARCH_X, HOST_OS_X describes the OS the VM is running on, which may be
different from the OS the VM is generating code for during AOT compilation.

Currently we conflate the two when emitting AOT as assembly, and we get away
with it because Flutter only uses assembly for target iOS and one can only
target iOS from a Mac, but we expect to use assembly for Android as well so
native tools can unwind Dart frames.
==========

to

==========
Rename TARGET_OS_* to HOST_OS_*.

Like HOST_ARCH_*, HOST_OS_* describes the OS the VM is running on, which may be
different from the OS the VM is generating code for during AOT compilation.

Currently we conflate the two when emitting AOT as assembly, and we get away
with it because Flutter only uses assembly for target iOS and one can only
target iOS from a Mac, but we expect to use assembly for Android as well so
native tools can unwind Dart frames.
==========

[rmacnak, 2017-03-14 22:37:51]

Description was changed from

==========
Rename TARGET_OS_* to HOST_OS_*.

Like HOST_ARCH_*, HOST_OS_* describes the OS the VM is running on, which may be
different from the OS the VM is generating code for during AOT compilation.

Currently we conflate the two when emitting AOT as assembly, and we get away
with it because Flutter only uses assembly for target iOS and one can only
target iOS from a Mac, but we expect to use assembly for Android as well so
native tools can unwind Dart frames.
==========

to

==========
Rename TARGET_OS_* to HOST_OS_*.

Like HOST_ARCH_*, HOST_OS_* describes the OS the VM is running on, which may be
different from the OS the VM is generating code for during AOT compilation.

Currently we conflate the two when emitting AOT as assembly, and we get away
with it because Flutter only uses assembly for target iOS and one can only
target iOS from a Mac, but we expect to use assembly for Android as well so
native tools can unwind Dart frames.
==========

[rmacnak, 2017-03-14 22:38:50]

Description was changed from

==========
Rename TARGET_OS_* to HOST_OS_*.

Like HOST_ARCH_*, HOST_OS_* describes the OS the VM is running on, which may be
different from the OS the VM is generating code for during AOT compilation.

Currently we conflate the two when emitting AOT as assembly, and we get away
with it because Flutter only uses assembly for target iOS and one can only
target iOS from a Mac, but we expect to use assembly for Android as well so
native tools can unwind Dart frames.
==========

to

==========
Rename TARGET_OS_* to HOST_OS_*.

Like HOST_ARCH_*, HOST_OS_* describes the OS the VM is running on, which may be
different from the OS the VM is generating code for during AOT compilation.

Currently we conflate the two when emitting AOT as assembly, and we get away
with it because Flutter only uses assembly for targeting iOS and one can only
target iOS from a Mac, but we expect to use assembly for Android as well so
native tools can unwind Dart frames.
==========

[rmacnak, 2017-03-15 01:02:40]

rmacnak@google.com changed reviewers:
+ fschneider@google.com, zra@google.com

[zra, 2017-03-15 16:54:44]

You'll have to update https://github.com/dart-lang/root_certificates first, and
roll it forward in the DEPS file in this CL. I think that might be all the other
places, but we'll have to be careful with this one.

[rmacnak, 2017-03-15 19:50:59]

On 2017/03/15 16:54:44, zra wrote:
> You'll have to update https://github.com/dart-lang/root_certificates first,
and
> roll it forward in the DEPS file in this CL. I think that might be all the
other
> places, but we'll have to be careful with this one.

Updated to DEPS in changes to root_certificates from
https://chromiumcodereview.appspot.com/2751143002/

[zra, 2017-03-15 19:56:04]

lgtm

[rmacnak, 2017-03-15 20:11:11]

Description was changed from

==========
Rename TARGET_OS_* to HOST_OS_*.

Like HOST_ARCH_*, HOST_OS_* describes the OS the VM is running on, which may be
different from the OS the VM is generating code for during AOT compilation.

Currently we conflate the two when emitting AOT as assembly, and we get away
with it because Flutter only uses assembly for targeting iOS and one can only
target iOS from a Mac, but we expect to use assembly for Android as well so
native tools can unwind Dart frames.
==========

to

==========
Rename TARGET_OS_* to HOST_OS_*.

Like HOST_ARCH_*, HOST_OS_* describes the OS the VM is running on, which may be
different from the OS the VM is generating code for during AOT compilation.

Currently we conflate the two when emitting AOT as assembly, and we get away
with it because Flutter only uses assembly for targeting iOS and one can only
target iOS from a Mac, but we expect to use assembly for Android as well so
native tools can unwind Dart frames.

R=zra@google.com

Committed:
https://github.com/dart-lang/sdk/commit/877284947b72bf719bc0defc5d97a6163b3f59e6
==========

[rmacnak, 2017-03-15 20:11:13]

Committed patchset #2 (id:20001) manually as
877284947b72bf719bc0defc5d97a6163b3f59e6 (presubmit successful).