Google Git
Sign in
llvm / llvm-project / 315d705b76089dfd29325637f820c2aa0eec0fe3
commit315d705b76089dfd29325637f820c2aa0eec0fe3[log] [tgz]
authorluobochuanqi <luobochuanqi@qq.com>Tue Nov 11 00:47:01 2025 +0800
committerGitHub <noreply@github.com>Mon Nov 10 19:47:01 2025 +0300
treef2fb5ebe920223eb5e8504ac63475aa61e68af2f
parentbb0bd382ab2ba6d8859106b3b347bc9e7e4dd976 [diff]
[clang-tidy] Move 'cert-msc51-cpp', 'cert-msc32-c' checks outside of 'cert' module and give a proper name (#167143)

…'cert' module and give a proper name

Summary:
This change addresses sub-issue #157296 of parent issue #157287, which
aims to clean up the `cert` module by moving checks that don't directly
map to CERT security standards to more appropriate modules.

The checks `cert-msc51-cpp` and `cert-msc32-c` both implement the same
logic to detect random number generators that are not properly seeded.
This is a generic bug pattern rather than a CERT-specific security
constraint, making it more suitable for the `bugprone` module.

Closes: #157296

---------

Co-authored-by: Baranov Victor <bar.victor.2002@gmail.com>
13 files changed
tree: f2fb5ebe920223eb5e8504ac63475aa61e68af2f
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. flang-rt/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libsycl/
  16. libunwind/
  17. lld/
  18. lldb/
  19. llvm/
  20. llvm-libgcc/
  21. mlir/
  22. offload/
  23. openmp/
  24. orc-rt/
  25. polly/
  26. runtimes/
  27. third-party/
  28. utils/
  29. .clang-format
  30. .clang-format-ignore
  31. .clang-tidy
  32. .git-blame-ignore-revs
  33. .gitattributes
  34. .gitignore
  35. .mailmap
  36. CODE_OF_CONDUCT.md
  37. CONTRIBUTING.md
  38. LICENSE.TXT
  39. pyproject.toml
  40. README.md
  41. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

Welcome to the LLVM project!

This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.

The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.

C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.

Other components include: the libc++ C++ standard library, the LLD linker, and more.

Getting the Source Code and Building LLVM

Consult the Getting Started with LLVM page for information on building and running LLVM.

For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.

Getting in touch

Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.

The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.