Closed
Bug 1476000
Opened 7 years ago
Closed 7 years ago
./mach build-warnings-list does not work with clang-cl builds
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(firefox63 fixed)
RESOLVED
FIXED
mozilla63
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | fixed |
People
(Reporter: emk, Assigned: emk)
References
Details
Attachments
(1 file)
|
2.30 KB,
patch
|
away
:
review+
|
Details | Diff | Splinter Review |
The build system cannot summarize warnings when clang-cl is used.
I _think_ we just need to add a new clang-cl regex to https://searchfox.org/mozilla-central/rev/b0275bc977ad7fda615ef34b822bba938f2b16fd/python/mozbuild/mozbuild/compilation/warnings.py#331
| Assignee | ||
Comment 2•7 years ago
|
||
This is an example of clang-cl warnings:
1:20.75 e:/m/mozilla-unified/widget/windows/JumpListBuilder.cpp(37,22): warning: unused variable 'kJumpListItemCID' [-Wunused-const-variable]
The differences from genuine MSVC are:
* A column number is present after a line number.
* Multiple spaces are present before the `warning` token.
* No error code (Cxxxx) is present after `warning`.
* An error flag (-Wxxxx) is present at the end of the error message.
Maybe a better comparison would be against genuine clang. This output looks pretty similar to `RE_CLANG_WARNING`, except the line/column is written as foo.cpp(1,2) instead of foo.cpp:1:2.
| Assignee | ||
Comment 4•7 years ago
|
||
| Assignee | ||
Updated•7 years ago
|
Assignee: nobody → VYV03354
Status: NEW → ASSIGNED
| Assignee | ||
Updated•7 years ago
|
Attachment #8992373 -
Flags: review?(dmajor)
Comment on attachment 8992373 [details] [diff] [review]
Support warnings format from clang-cl
If this works for you locally, then it seems fine to me.
Attachment #8992373 -
Flags: review?(dmajor) → review+
Pushed by VYV03354@nifty.ne.jp:
https://hg.mozilla.org/integration/mozilla-inbound/rev/896f75ea7634
Support warnings format from clang-cl. r=dmajor
Comment 7•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in
before you can comment on or make changes to this bug.
Description
•