Revision tags: llvmorg-18.1.8, llvmorg-18.1.7, llvmorg-18.1.6, llvmorg-18.1.5, llvmorg-18.1.4, llvmorg-18.1.3, llvmorg-18.1.2, llvmorg-18.1.1, llvmorg-18.1.0, llvmorg-18.1.0-rc4, llvmorg-18.1.0-rc3, llvmorg-18.1.0-rc2, llvmorg-18.1.0-rc1, llvmorg-19-init, llvmorg-17.0.6, llvmorg-17.0.5 |
|
#
c92cf315 |
| 03-Nov-2023 |
michaelrj-google <71531609+michaelrj-google@users.noreply.github.com> |
[clang-tidy][libc] Ignore implicit function inline (#71095)
This patch adjusts the inline function decl check for LLVM libc to ignore implicit functions. For the moment the plan is to ignore these a
[clang-tidy][libc] Ignore implicit function inline (#71095)
This patch adjusts the inline function decl check for LLVM libc to ignore implicit functions. For the moment the plan is to ignore these and mark the class with a macro so that it can be given the appropriate properties without explicitly defining all its ctors/dtors.
show more ...
|
Revision tags: llvmorg-17.0.4, llvmorg-17.0.3, llvmorg-17.0.2, llvmorg-17.0.1, llvmorg-17.0.0, llvmorg-17.0.0-rc4, llvmorg-17.0.0-rc3, llvmorg-17.0.0-rc2 |
|
#
9d4162ff |
| 05-Aug-2023 |
Roland McGrath <mcgrathr@google.com> |
[clang-tidy] Add fix-it support to `llvmlibc-inline-function-decl`
This is very simplistic and could be more thorough by replacing an existing `LIBC_INLINE` in the wrong location or a redunant `inli
[clang-tidy] Add fix-it support to `llvmlibc-inline-function-decl`
This is very simplistic and could be more thorough by replacing an existing `LIBC_INLINE` in the wrong location or a redunant `inline` when inserting the right macro use. But as is this suffices to automatically apply fixes for most or all of the instances in the libc tree today and get working results (despite some superfluous `inline` keywords left behind).
Reviewed By: abrachet
Differential Revision: https://reviews.llvm.org/D157164
show more ...
|
Revision tags: llvmorg-17.0.0-rc1, llvmorg-18-init |
|
#
c96306db |
| 18-Jun-2023 |
AMS21 <AMS21.github@gmail.com> |
[clang-tidy] Fix `llvmlibc-inline-function-decl` false positives for templated function definitions
For a declaration the `FunctionDecl` begin location does not include the template parameter lists,
[clang-tidy] Fix `llvmlibc-inline-function-decl` false positives for templated function definitions
For a declaration the `FunctionDecl` begin location does not include the template parameter lists, but for some reason if you have a separate definitions to the declaration the begin location does include them. With this patch we now correctly handle that case.
This fixes llvm#62746
Reviewed By: PiotrZSL
Differential Revision: https://reviews.llvm.org/D153218
show more ...
|
Revision tags: llvmorg-16.0.6, llvmorg-16.0.5, llvmorg-16.0.4, llvmorg-16.0.3, llvmorg-16.0.2 |
|
#
1663016b |
| 17-Apr-2023 |
Joseph Huber <jhuber6@vols.utk.edu> |
[clang-tidy] Prevent `llvmlibc-inline-function-decl` triggering on lambdas
The `llvmlibc-inline-function-decl` check is intended to be used to allow declarations in the `libc` project's header to be
[clang-tidy] Prevent `llvmlibc-inline-function-decl` triggering on lambdas
The `llvmlibc-inline-function-decl` check is intended to be used to allow declarations in the `libc` project's header to be changed per-TU. However, it is impossible to place this macro in front of a lambda so this is not helpful. Additionally, lambdas are always going to have internal linkage so they will not differ accross TUs.
Fixes https://github.com/llvm/llvm-project/issues/62147
Reviewed By: lntue, PiotrZSL
Differential Revision: https://reviews.llvm.org/D148444
show more ...
|
Revision tags: llvmorg-16.0.1, llvmorg-16.0.0, llvmorg-16.0.0-rc4, llvmorg-16.0.0-rc3, llvmorg-16.0.0-rc2, llvmorg-16.0.0-rc1, llvmorg-17-init |
|
#
5b37cddf |
| 25-Jan-2023 |
Carlos Galvez <carlosgalvezp@gmail.com> |
[clang-tidy] Introduce HeaderFileExtensions and ImplementationFileExtensions options
Re-introduce the patch that was reverted previously. In the first attempt, the checks would not be able to read f
[clang-tidy] Introduce HeaderFileExtensions and ImplementationFileExtensions options
Re-introduce the patch that was reverted previously. In the first attempt, the checks would not be able to read from the global option, since getLocalOrGlobal only works with string types. Additional logic is needed in order to support both use cases in the transition period. All that logic will be removed when the local options are fully removed.
We have a number of checks designed to analyze problems in header files only, for example:
bugprone-suspicious-include google-build-namespaces llvm-header-guard misc-definitions-in-header ...
All these checks duplicate the same logic and options to determine whether a location is placed in the main source file or in the header. More checks are coming up with similar requirements.
Thus, to remove duplication, let's move this option to the top-level configuration of clang-tidy (since it's something all checks should share).
Add a deprecation notice for all checks that use the local option, prompting to update to the global option.
Differential Revision: https://reviews.llvm.org/D142655
show more ...
|
#
b7b28c6c |
| 26-Jan-2023 |
Siva Chandra Reddy <sivachandra@google.com> |
[clang-tidy][libc] Add an inline function checker for the libc project.
The new checker checks if inline functions defined in header files are tagged with the LIBC_INLINE macro. See https://libc.llv
[clang-tidy][libc] Add an inline function checker for the libc project.
The new checker checks if inline functions defined in header files are tagged with the LIBC_INLINE macro. See https://libc.llvm.org/code_style.html for more information about this macro.
Reviewed By: carlosgalvezp
Differential Revision: https://reviews.llvm.org/D142592
show more ...
|