| OLD | NEW |
|---|
| 1 # Retrieving Code Analysis Warnings | 1 # Retrieving Code Analysis Warnings |
| 2 | 2 |
| 3 Several times a day the Chromium code base is built with Microsoft VC++'s | 3 Several times a day the Chromium code base is built with Microsoft VC++'s |
| 4 `/analyze` compile option. This does static code analysis which has found | 4 `/analyze` compile option. This does static code analysis which has found |
| 5 numerous bugs (see https://crbug.com/427616). While it is possible to visit the | 5 numerous bugs (see https://crbug.com/427616). While it is possible to visit the |
| 6 `/analyze` builder page and look at the raw results | 6 `/analyze` builder page and look at the raw results |
| 7 (http://build.chromium.org/p/chromium.fyi/builders/Chromium%20Windows%20Analyze) | 7 (https://build.chromium.org/p/chromium.fyi/builders/Chromium%20Windows%20Analyze
) |
| 8 this works very poorly. | 8 this works very poorly. |
| 9 | 9 |
| 10 As of this writing there are 2,702 unique warnings. Some of these are in header | 10 As of this writing there are 2,702 unique warnings. Some of these are in header |
| 11 files and fire multiple times so there are a total of 11,202 warning lines. Most | 11 files and fire multiple times so there are a total of 11,202 warning lines. Most |
| 12 of these have been examined and found to be false positives. Therefore, in order | 12 of these have been examined and found to be false positives. Therefore, in order |
| 13 to sanely examine the /analyze warnings it is necessary to summarize the | 13 to sanely examine the /analyze warnings it is necessary to summarize the |
| 14 warnings, and find what is new. | 14 warnings, and find what is new. |
| 15 | 15 |
| 16 There are scripts to do this. | 16 There are scripts to do this. |
| 17 | 17 |
| (...skipping 39 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 57 ideal. | 57 ideal. |
| 58 | 58 |
| 59 Some of the warnings say that out-of-range memory accesses will occur, which is | 59 Some of the warnings say that out-of-range memory accesses will occur, which is |
| 60 pretty scary. For instance "warning C6201: Index '-1' is out of valid index | 60 pretty scary. For instance "warning C6201: Index '-1' is out of valid index |
| 61 range '0' to '4'". In most cases these are false positives so use your own | 61 range '0' to '4'". In most cases these are false positives so use your own |
| 62 judgment when deciding whether to fix them. | 62 judgment when deciding whether to fix them. |
| 63 | 63 |
| 64 The `full.txt` file contains the raw output and should usually be ignored. | 64 The `full.txt` file contains the raw output and should usually be ignored. |
| 65 | 65 |
| 66 If you have any questions then post to the chromium dev mailing list. | 66 If you have any questions then post to the chromium dev mailing list. |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2545363002:
Use HTTPS links for Google domains in docs (Closed)
