Add -fms-compatibility-version=19 to the clang-cl self-host

Add -fms-compatibility-version=19 to the clang-cl self-host

Otherwise, we get errors about char16_t and char32_t during the stage 2
build.

Also, fix a bug where cflags, cxxflags, and ldflags all pointed to the
same list.
R=hans@chromium.org
BUG=597854
Committed: https://chromium.googlesource.com/chromium/src/+/9be8ca7b77549c46f9a51e991d25e1a509664fd5

[hans, 2016-03-25 16:22:27]

lgtm

[Reid Kleckner, 2016-03-25 16:47:38]

Description was changed from

==========
Add -fms-compatibility-version=19 to the clang-cl self-host

Otherwise, we get errors about char16_t and char32_t during the stage 2
build.

R=hans@chromium.org
BUG=597854
==========

to

==========
Add -fms-compatibility-version=19 to the clang-cl self-host

Otherwise, we get errors about char16_t and char32_t during the stage 2
build.

Also, fix a bug where cflags, cxxflags, and ldflags all pointed to the
same list.
R=hans@chromium.org
BUG=597854
==========

[Reid Kleckner, 2016-03-25 16:47:45]

The CQ bit was checked by rnk@chromium.org

[Reid Kleckner, 2016-03-25 16:47:45]

The patchset sent to the CQ was uploaded after l-g-t-m from hans@chromium.org
Link to the patchset: https://codereview.chromium.org/1832093002/#ps20001
(title: "Fix a bug list thing")

[commit-bot: I haz the power, 2016-03-25 16:47:59]

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

[commit-bot: I haz the power, 2016-03-25 16:56:11]

Description was changed from

==========
Add -fms-compatibility-version=19 to the clang-cl self-host

Otherwise, we get errors about char16_t and char32_t during the stage 2
build.

Also, fix a bug where cflags, cxxflags, and ldflags all pointed to the
same list.
R=hans@chromium.org
BUG=597854
==========

to

==========
Add -fms-compatibility-version=19 to the clang-cl self-host

Otherwise, we get errors about char16_t and char32_t during the stage 2
build.

Also, fix a bug where cflags, cxxflags, and ldflags all pointed to the
same list.
R=hans@chromium.org
BUG=597854

Committed: https://crrev.com/9be8ca7b77549c46f9a51e991d25e1a509664fd5
Cr-Commit-Position: refs/heads/master@{#383288}
==========

[commit-bot: I haz the power, 2016-03-25 16:56:12]

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

[Reid Kleckner, 2016-03-25 16:57:04]

Description was changed from

==========
Add -fms-compatibility-version=19 to the clang-cl self-host

Otherwise, we get errors about char16_t and char32_t during the stage 2
build.

Also, fix a bug where cflags, cxxflags, and ldflags all pointed to the
same list.
R=hans@chromium.org
BUG=597854

Committed: https://crrev.com/9be8ca7b77549c46f9a51e991d25e1a509664fd5
Cr-Commit-Position: refs/heads/master@{#383288}
==========

to

==========
Add -fms-compatibility-version=19 to the clang-cl self-host

Otherwise, we get errors about char16_t and char32_t during the stage 2
build.

Also, fix a bug where cflags, cxxflags, and ldflags all pointed to the
same list.
R=hans@chromium.org
BUG=597854

Committed:
https://chromium.googlesource.com/chromium/src/+/9be8ca7b77549c46f9a51e991d25...
==========

[Reid Kleckner, 2016-03-25 16:57:05]

Committed patchset #2 (id:20001) manually as
9be8ca7b77549c46f9a51e991d25e1a509664fd5 (presubmit successful).

[Nico, 2016-03-25 19:53:31]

On 2016/03/25 16:57:05, Reid Kleckner wrote:
> Committed patchset #2 (id:20001) manually as
> 9be8ca7b77549c46f9a51e991d25e1a509664fd5 (presubmit successful).

Should the fmsc bits be in the upstream cmake config? Everyone doing bootstraps
on Windows will need this, right?

[Reid Kleckner, 2016-03-25 22:50:02]

On 2016/03/25 19:53:31, Nico (away until Mon Mar 27) wrote:
> On 2016/03/25 16:57:05, Reid Kleckner wrote:
> > Committed patchset #2 (id:20001) manually as
> > 9be8ca7b77549c46f9a51e991d25e1a509664fd5 (presubmit successful).
> 
> Should the fmsc bits be in the upstream cmake config? Everyone doing
bootstraps
> on Windows will need this, right?

Yes, but I didn't want to pick a new LLVM revision. We can copy the cmake bits I
added to compiler-rt, and remove this later.