bcm5719-llvm/clang-tools-extra/docs, branch meklort-10.0.1

Add new website to release notes.

2020-03-16T10:51:51+00:00

ReleaseNotes: remove in-progress warnings, tidy up a bit

2020-02-28T16:11:03+00:00

[docs] clangd release notes

2020-02-25T14:49:43+00:00

Added readability-qualified-auto check

2020-01-14T19:06:46+00:00

Adds a check that detects any auto variables that are deduced to a pointer or a const pointer then adds in the const and asterisk according. Will also check auto L value references that could be written as const. This relates to the coding standard https://llvm.org/docs/CodingStandards.html#beware-unnecessary-copies-with-auto

clang-tidy doc: unbreak the CI

2020-01-10T21:25:01+00:00

clang-tidy doc: Refresh the list of checkers and polish the script

2020-01-10T21:07:47+00:00

Restore order in clang-tidy section of release notes

2020-01-10T08:19:58+00:00

Major changes are introduction of subsubsections to prevent people putting new entries in wrong places. I also polished line length and highlighting. Patch by Eugene Zelenko!

clang-tidy doc - remove the widths

2020-01-10T07:11:05+00:00

[clang-tidy] modernize-use-using uses AST and now supports struct defintions and multiple types in a typedef

2020-01-07T21:36:11+00:00

Summary: It now handles `typedef`s that include comma-separated multiple types, and handles embedded struct definitions, which previously could not be automatically converted. For example, with this patch `modernize-use-using` now can convert: typedef struct { int a; } R_t, *R_p; to: using R_t = struct { int a; }; using R_p = R_t*; `-ast-dump` showed that the `CXXRecordDecl` definitions and multiple `TypedefDecl`s come consecutively in the tree, so `check()` stores information between calls to determine when it is receiving a second or additional `TypedefDecl` within a single `typedef`, or when the current `TypedefDecl` refers to an embedded `CXXRecordDecl` like a `struct`. Reviewers: alexfh, aaron.ballman Patch by: poelmanc Subscribers: riccibruno, sammccall, cfe-commits, aaron.ballman Tags: clang-tools-extra, clang Differential Revision: https://reviews.llvm.org/D70270

[clang-tidy] new check: bugprone-signed-char-misuse

2020-01-06T17:21:26+00:00

Summary: This check searches for signed char -> integer conversions which might indicate programming error, because of the misinterpretation of char values. A signed char might store the non-ASCII characters as negative values. The human programmer probably expects that after an integer conversion the converted value matches with the character code (a value from [0..255]), however, the actual value is in [-128..127] interval. See also: STR34-C. Cast characters to unsigned char before converting to larger integer sizes By now this check is limited to assignment / variable declarations. If we would catch all signed char -> integer conversion, then it would produce a lot of findings and also false positives. So I added only this use case now, but this check can be extended with additional use cases later. The CERT documentation mentions another use case when the char is used for array subscript. Next to that a third use case can be the signed char - unsigned char comparison, which also a use case where things happen unexpectedly because of conversion to integer. Reviewers: alexfh, hokein, aaron.ballman Reviewed By: aaron.ballman Subscribers: sylvestre.ledru, whisperity, Eugene.Zelenko, mgorny, xazax.hun, cfe-commits Tags: #clang, #clang-tools-extra Differential Revision: https://reviews.llvm.org/D71174