Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: danmar/cppcheck
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: nirbar/cppcheck
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 3 commits
  • 15 files changed
  • 1 contributor

Commits on May 24, 2016

  1. Add feature: Cache check results for subsequent checks:

    - Add command line flag: --cache=path/to/cache.xml
    - Each check is cached along side the check file's size, preprocessed code hash (SHA-512), configuration, check results
    - In subsequent runs, if a file with the same path, size, hash is found in cache- report the cached results rather than running the full check again.
    - File hash and size are calculated on preprocessed code. This ensures that the file hasn't changed as well as the included files.
    - Results are cached disregarding uniquity. This allows subsequent runs with different configuration-sets to have all the results available. Report output is still unique- just the cache isn't.
    - File path must be exact across runs. (either use same relative paths or same full path)
    nirbar committed May 24, 2016
    Configuration menu
    Copy the full SHA
    d30dfaa View commit details
    Browse the repository at this point in the history
  2. - Add command line flag: --cache=path/to/cache.xml

    - Each check is cached along side the file's pre-processed size, code hash (SHA-512), configuration, check results
    - In subsequent runs, if a file with the same path, size, hash is found in cache- report the cached results rather than running the full check again.
    - File hash and size are calculated on preprocessed code. This ensures that the file hasn't changed as well as the included files.
    - Results are cached disregarding uniquity. This allows subsequent runs with different configuration-sets to have all the results available. Report output is still unique- just the cache isn't.
    - File path must be exact across runs. (either use same relative paths or same full path)
    nirbar committed May 24, 2016
    Configuration menu
    Copy the full SHA
    93cf239 View commit details
    Browse the repository at this point in the history

Commits on May 31, 2016

  1. Report cached errors in headers multiple times when included in multi…

    …ple source files.
    
    This somewhat reduces unique repoting, but follows full-scan convention.
    nirbar committed May 31, 2016
    Configuration menu
    Copy the full SHA
    f172bc1 View commit details
    Browse the repository at this point in the history
Loading