microsoft / ShaderConductor
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
hlsl
glsl
txt
cmake
hlsli
clang-format
gitattributes
  • 17 extensions are included in analyses: hlsl, glsl, txt, cmake, hlsli, cpp, md, gitignore, cs, yml, svg, clang-format, h, py, hpp, gitattributes, json
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (6 files).
    • exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
    • exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (7 files).
Overview of Analyzed Files
Basic stats on analyzed files
Intro
For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

  • The main category contains all manually created source code files that are being used in the production.
  • Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
  • Test source code files are used only for testing of the product. These files are normally not deployed to production.
  • Build and deployment source code files are used to configure or support build and deployment process.
  • Generated source code files are automatically generated files that have not been manually changed after generation.
  • While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
  • Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

main2429 LOC (49%) 17 files
test1902 LOC (38%) 66 files
generated0 LOC (0%) 0 files
build and deployment0 LOC (0%) 0 files
other569 LOC (11%) 3 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
cmake
hlsl
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 17 files match defined criteria (2,429 lines of code, 100.0% vs. main code):
    • 3 *.cpp files (1,328 lines of code)
    • 2 *.yml files (268 lines of code)
    • 1 *.py files (232 lines of code)
    • 1 *.hpp files (192 lines of code)
    • 2 *.cs files (187 lines of code)
    • 6 *.cmake files (137 lines of code)
    • 1 *.h files (53 lines of code)
    • 1 *.hlsl files (32 lines of code)
  • " *.cpp" is biggest, containing 54.67% of code.
  • " *.hlsl" is smallest, containing 1.32% of code.


*.cpp1328 LOC (54%) 3 files
*.yml268 LOC (11%) 2 files
*.py232 LOC (9%) 1 files
*.hpp192 LOC (7%) 1 files
*.cs187 LOC (7%) 2 files
*.cmake137 LOC (5%) 6 files
*.h53 LOC (2%) 1 files
*.hlsl32 LOC (1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
hlsl
glsl
hlsli
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]ests/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 66 files match defined criteria (1,902 lines of code, 78.3% vs. main code):
    • 36 *.hlsl files (837 lines of code)
    • 25 *.glsl files (550 lines of code)
    • 1 *.cpp files (503 lines of code)
    • 4 *.hlsli files (12 lines of code)
  • " *.hlsl" is biggest, containing 44.01% of code.
  • " *.hlsli" is smallest, containing 0.63% of code.


*.hlsl837 LOC (44%) 36 files
*.glsl550 LOC (28%) 25 files
*.cpp503 LOC (26%) 1 files
*.hlsli12 LOC (<1%) 4 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]md".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]svg".
    • files with paths like ".*/README[.][a-z0-9]+".
  • 3 files match defined criteria (569 lines of code, 23.4% vs. main code):
    • 1 *.svg files (490 lines of code)
    • 2 *.md files (79 lines of code)
  • " *.svg" is biggest, containing 86.12% of code.
  • " *.md" is smallest, containing 13.88% of code.


*.svg490 LOC (86%) 1 files
*.md79 LOC (13%) 2 files
Analyzers
Info about analyzers used for source code examinations.
  • *.cpp files are analyzed with CppAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis
  • *.yml files are analyzed with YamlAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.py files are analyzed with PythonAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis
  • *.hpp files are analyzed with CppAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis
  • *.cs files are analyzed with CSharpAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis (based on namespace heuristics)
  • *.cmake files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.h files are analyzed with CppAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis
  • *.hlsl files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis


2022-01-30 22:25