[all-commits] [llvm/llvm-project] 6540c9: [NFC][analyzer] Update docs of CodeChecker --ctu-a...

[Donát Nagy via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 6540c93aa991dbc2b09cc5395493dadd7181551e
      https://github.com/llvm/llvm-project/commit/6540c93aa991dbc2b09cc5395493dadd7181551e
  Author: Donát Nagy <donat.nagy at ericsson.com>
  Date:   2025-07-31 (Thu, 31 Jul 2025)

  Changed paths:
    M clang/docs/analyzer/user-docs/CrossTranslationUnit.rst

  Log Message:
  -----------
  [NFC][analyzer] Update docs of CodeChecker --ctu-ast-mode (#144901)

The documentation of the cross translation unit analysis mentioned a
certain flag of `CodeChecker` (an external open source tool that can be
used to drive the static analysis), but the information about it was
obsolete: apparently the name of the flag, the names of the possible
values, and the default value were all changed.

Currently `CodeChecker analyze --help` displays this flag as
```
--ctu-ast-mode {load-from-pch,parse-on-demand}
  Choose the way ASTs are loaded during CTU analysis. Only available if
  CTU mode is enabled. Mode 'load-from-pch' generates PCH format
  serialized ASTs during the 'collect' phase. Mode 'parse-on-demand'
  only generates the invocations needed to parse the ASTs. Mode 'load-
  from-pch' can use significant disk-space for the serialized ASTs,
  while mode 'parse-on-demand' can incur some runtime CPU overhead in
  the second phase of the analysis. (default: parse-on-demand)
```
and I tried to follow this in the commands that I adjusted.

Note that this documentation file probably contains other obsolete
details as well, but I didn't try to find or fix them.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications