New issue
Advanced search Search tips

Issue 768616 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

use consistent compiler settings on clang for all platforms

Project Member Reported by wfh@chromium.org, Sep 25 2017

Issue description

there's a few instances in BUILD.gn that I saw recently where "is_win" is used to set up compiler warnings and compiler flags, assuming that the compiler will be MSVC, when in fact it could be clang.

I suspect a lot of the 'is_win' could be changed to 'is_vc' when they directly change compiler options.

example: https://cs.chromium.org/chromium/src/third_party/skia/gn/BUILD.gn?sq=package:chromium&dr=C&l=272 it would appear that on win/clang the extended clang warnings (starting on L301) are never enabled.

I wonder if we should go through BUILD files and make sure is_win is not assuming MSVC?
 

Comment 1 by thakis@chromium.org, Sep 26 2017

I did that a few times. In general, clang-cl takes cl-compatible flags and ignores some (eg most but not all warning flags). Unless you have something concrete, I think this is wontfix.

Sign in to add a comment