Disable /analyze when building with clang

Disable /analyze when building with clang

When doing x64 builds of Chrome with VC++ we compile some modules
(currently just libyuv) with clang, in order to get inline assembly
support. This causes problems on /analyze builds because clang-cl
doesn't understand the /analyze compiler switches. This change
disables /analyze for those files that are compiled with clang.

With this change I can do a /analyze build of libyuv without
hitting any errors, but warnings are emitted as appropriate.

R=brettw@chromium.org
BUG=427616
Review-Url: https://codereview.chromium.org/2786733005
Cr-Commit-Position: refs/heads/master@{#460874}
Committed: https://chromium.googlesource.com/chromium/src/+/bb4bb0ebf2bfc2881100122e1513ee3f694744a0

[brucedawson, 2017-03-29 23:07:23]

The CQ bit was checked by brucedawson@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-03-29 23:08:14]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[brucedawson, 2017-03-29 23:08:47]

Description was changed from

==========
Disable /analyze when building with clang

When doing x64 builds of Chrome with VC++ we compile some modules
(currently just libyuv) with clang, in order to get inline assembly
support. This causes problems on /analyze builds because clang-cl
doesn't understand the /analyze compiler switches. This change
disables /analyze for those files that are compiled with clang.

R=brettw@chromium.org
BUG=427616
==========

to

==========
Disable /analyze when building with clang

When doing x64 builds of Chrome with VC++ we compile some modules
(currently just libyuv) with clang, in order to get inline assembly
support. This causes problems on /analyze builds because clang-cl
doesn't understand the /analyze compiler switches. This change
disables /analyze for those files that are compiled with clang.

With this change I can do a /analyze build of libyuv without
hitting any errors, but warnings are emitted as appropriate.

R=brettw@chromium.org
BUG=427616
==========

[brucedawson, 2017-03-29 23:09:24]

Your comment on the libyuv CL made me realize that the /analyze part of the
problem can be solved *much* more simply. This CL works.

[commit-bot: I haz the power, 2017-03-30 01:24:46]

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

[commit-bot: I haz the power, 2017-03-30 01:24:46]

Dry run: This issue passed the CQ dry run.

[brettw, 2017-03-30 20:46:30]

lgtm

[brucedawson, 2017-03-30 20:54:58]

The CQ bit was checked by brucedawson@chromium.org

[commit-bot: I haz the power, 2017-03-30 20:56:36]

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-03-30 21:06:59]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490907298335760, "parent_rev":
"5d663f46bd1cef7b00e9a52b5148af16014ec652", "commit_rev":
"bb4bb0ebf2bfc2881100122e1513ee3f694744a0"}

[commit-bot: I haz the power, 2017-03-30 21:07:48]

Description was changed from

==========
Disable /analyze when building with clang

When doing x64 builds of Chrome with VC++ we compile some modules
(currently just libyuv) with clang, in order to get inline assembly
support. This causes problems on /analyze builds because clang-cl
doesn't understand the /analyze compiler switches. This change
disables /analyze for those files that are compiled with clang.

With this change I can do a /analyze build of libyuv without
hitting any errors, but warnings are emitted as appropriate.

R=brettw@chromium.org
BUG=427616
==========

to

==========
Disable /analyze when building with clang

When doing x64 builds of Chrome with VC++ we compile some modules
(currently just libyuv) with clang, in order to get inline assembly
support. This causes problems on /analyze builds because clang-cl
doesn't understand the /analyze compiler switches. This change
disables /analyze for those files that are compiled with clang.

With this change I can do a /analyze build of libyuv without
hitting any errors, but warnings are emitted as appropriate.

R=brettw@chromium.org
BUG=427616

Review-Url: https://codereview.chromium.org/2786733005
Cr-Commit-Position: refs/heads/master@{#460874}
Committed:
https://chromium.googlesource.com/chromium/src/+/bb4bb0ebf2bfc2881100122e1513...
==========

[commit-bot: I haz the power, 2017-03-30 21:07:49]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/bb4bb0ebf2bfc2881100122e1513...