llvm/llvm-project

21 other commands the scanner could not classify

Commands from CI steps and task runners that look like checks but match no known tool. Some are checks, some are not.

• abi-compliance-checker $EXTRA_ARGS -l libLLVM.so -old build-baseline/*.abi -new build-latest/*.abi
• abi-compliance-checker -lib $lib -old build-baseline/$lib*.abi -new build-latest/$lib*.abi
• bash -c echo Running project checks targets: $WINDOWS_CHECK_TARGETS
• bash -c echo Running runtimes checks targets: $WINDOWS_RUNTIMES_CHECK_TARGETS
• bazelisk test --config=ci --sandbox_base= --remote_cache=https://storage.googleapis.com/$CACHE_GCS_BUCKET-bazel --goo...
• cmake -GNinja -DCMAKE_BUILD_TYPE=Release ../llvm
• cmake ../llvm -DCMAKE_BUILD_TYPE=Release -G Ninja
• do echo Still checking out the test-suite...
• do echo Still running the test-suite...
• ninja check-hlsl-unit
• ninja check-llvm-tools-dxil-dis
• ninja split-file FileCheck
• python ./.github/workflows/release-asset-audit.py $GITHUB_TOKEN
• python ./llvm-project/llvm/utils/git/ids-check-helper.py --token $EXPR --issue-number $GITHUB_PR_NUMBER --idt-path $(...
• python ./llvm/utils/git/code-format-helper.py --write-comment-to-file --token $EXPR --issue-number $GITHUB_PR_NUMBER ...
• python llvm-test-suite/utils/lnt/run-test-suite.py ${LNT_MACHINE} --no-auto-name --succinct-compile-output --sandbox ...
• python llvm/utils/git/code-lint-helper.py --token $EXPR --issue-number $GITHUB_PR_NUMBER --start-rev HEAD~1 --end-rev...
• scan-build --generate-index-only build/analyzer-results
• sha256sum --check
• shasum --check -
• test-suite diff from $BASE_SHA...$HEAD_SHA: $ARTIFACT_URL

full scan as JSON

• Avoid unnecessary autoUse explicit types instead of `auto` unless the type is obvious from the right-hand side of the assignment or impossible to spell. The LL...

  llvm/llvm-project Code Style C++ runtimes 2025-07-28

  copy raw open
• Use descriptive namesChoose names that clearly describe the purpose, behavior, and content of functions, variables, and constants. Names should be self-docume...

  llvm/llvm-project Naming Conventions C++ runtimes 2025-07-28

  copy raw open
• avoid unnecessary allocationsMinimize performance overhead by avoiding unnecessary memory allocations, expensive data structures, and redundant object creation. Choos...

  llvm/llvm-project Performance Optimization C++ runtimes 2025-07-28

  copy raw open
• comprehensive test coverageTests should comprehensively cover all relevant scenarios, including return values, edge cases, different compilation modes, and abnormal...

  llvm/llvm-project Testing C++ runtimes 2025-07-24

  copy raw open
• Provide contextual code documentationCode should include documentation that explains the purpose, rationale, and context behind implementation decisions, not just what the co...

  llvm/llvm-project Documentation C++ runtimes 2025-07-25

  copy raw open
• cost-based algorithmic decisionsWhen implementing algorithmic transformations and optimizations, use cost analysis and profitability heuristics to guide decision-making ...

  llvm/llvm-project Algorithms Other runtimes 2025-07-28

  copy raw open
• minimize header dependenciesOrganize code to minimize header dependencies and improve compilation times. Use forward declarations instead of includes when possible, ...

  llvm/llvm-project Code Style Other runtimes 2025-07-28

  copy raw open
• Use descriptive semantic namesChoose specific, meaningful names that clearly convey purpose and follow established codebase patterns. Avoid generic terms that could ap...

  llvm/llvm-project Naming Conventions Other runtimes 2025-07-28

  copy raw open
• Design thoughtful API interfacesWhen designing APIs, prioritize clarity, appropriate abstraction levels, and user experience. Avoid magic numbers or unclear parameters b...

  llvm/llvm-project API C++ runtimes 2025-07-25

  copy raw open
• Eliminate redundant null checksAvoid unnecessary null checks when the called function already handles null cases, and use references instead of pointers when null value...

  llvm/llvm-project Null Handling C++ runtimes 2025-07-25

  copy raw open
• proper error propagationEnsure errors are properly propagated to callers rather than handled locally with exits or fatal errors. Library functions should return ...

  llvm/llvm-project Error Handling C++ runtimes 2025-07-25

  copy raw open
• Configuration completeness validationEnsure configuration options are complete and properly validated before use. When implementing configuration parsing or option handling, ...

  llvm/llvm-project Configurations C++ runtimes 2025-07-28

  copy raw open
• optimize computational complexityWhen implementing algorithms, be mindful of computational complexity and optimize for efficiency by avoiding expensive operations and reu...

  llvm/llvm-project Algorithms C++ runtimes 2025-07-28

  copy raw open
• minimize test complexityTests should be minimal and focused on the specific functionality being verified. Remove unnecessary passes, tools, or operations that ar...

  llvm/llvm-project Testing Other runtimes 2025-07-28

  copy raw open
• Target-aware configuration handlingWhen implementing features that depend on specific compilation targets or modes, design configuration mechanisms that gracefully handle t...

  llvm/llvm-project Configurations Other runtimes 2025-07-11

  copy raw open
• Choose appropriate string typesSelect the most efficient string type based on ownership and lifetime requirements to optimize memory usage and prevent safety issues. Us...

  llvm/llvm-project Performance Optimization Other runtimes 2025-07-28

  copy raw open
• explicit invalid value handlingWhen designing enums or working with type casting, explicitly define and handle invalid states rather than relying on undefined behavior....

  llvm/llvm-project Null Handling Other runtimes 2025-07-28

  copy raw open
• match API complexity appropriatelyDesign APIs with complexity that matches their actual use cases and adopt established patterns that improve clarity. Avoid over-engineeri...

  llvm/llvm-project API Other runtimes 2025-07-28

  copy raw open
• preserve known test issuesWhen tests exhibit known false positives or false negatives, preserve these test cases with clear documentation rather than removing them...

  llvm/llvm-project Testing C runtimes 2025-07-28

  copy raw open
• specify network protocol endiannessAlways explicitly specify byte order (endianness) in network protocol documentation and implementations. Even when a specification mandat...

  llvm/llvm-project Networking Markdown runtimes 2025-07-28

  copy raw open
• structure contextual log messagesLog messages should include sufficient contextual information and structured formatting to enable effective debugging and filtering. This...

  llvm/llvm-project Logging Other runtimes 2025-07-28

  copy raw open
• Write accessible documentationDocumentation should be written with clarity and completeness to serve readers who may not have deep domain expertise. Use precise, unamb...

  llvm/llvm-project Documentation Markdown runtimes 2025-07-28

  copy raw open
• Explicit configuration requirementsAlways specify explicit configuration parameters rather than relying on default settings that may vary across different build environment...

  llvm/llvm-project Configurations C runtimes 2025-07-27

  copy raw open
• improve code readabilityWhen code expressions become complex or difficult to understand at first glance, refactor them for better readability. This can be achiev...

  llvm/llvm-project Code Style Python runtimes 2025-07-27

  copy raw open
• protect shared dataAlways protect shared data that can be accessed by multiple threads using appropriate synchronization mechanisms. Identify potential race...

  llvm/llvm-project Concurrency C++ runtimes 2025-07-24

  copy raw open
• Match function names to behaviorFunction names and their documentation must accurately reflect what the function actually does. When a function handles more data than it...

  llvm/llvm-project Naming Conventions TypeScript runtimes 2025-07-22

  copy raw open
• Ensure comprehensive documentationDocumentation should be complete, properly formatted, and clearly explain purpose with adequate examples. When writing documentation, ens...

  llvm/llvm-project Documentation Other runtimes 2025-06-19

  copy raw open
• consistent error diagnosticsWhen implementing attributes, language features, or compiler diagnostics, always provide explicit error diagnostics rather than default w...

  llvm/llvm-project Error Handling Other runtimes 2025-06-15

  copy raw open