Skip to content
Snippets Groups Projects
  1. Feb 14, 2017
  2. Jan 29, 2017
  3. Jan 28, 2017
  4. Sep 24, 2016
  5. Sep 14, 2016
    • Devin Coughlin's avatar
      [analyzer] scan-build-py: Remove relative path hack for SATestsBuild.py · 82d5b51e
      Devin Coughlin authored
      Remove the relative path hack in scan-build-py that converts a fully qualified
      directory name and a fully qualified file path to a relative path before running
      the analyzer on a file.
      
      This hack is not needed: the bad interaction with SATestsBuild.py it was
      intended to address is actually the same underlying problem that r280768 fixed.
      Further, because the hack would always relativize paths, it caused
      SATestBuild.py to be unable to properly line up issues when the build system
      changed directory and then built a source file in a child directory but used a
      fully-qualified path for the source file.
      
      Differential Revision: https://reviews.llvm.org/D24470
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@281516 91177308-0d34-0410-b5e6-96231b3b80d8
      82d5b51e
  6. Sep 07, 2016
    • Devin Coughlin's avatar
      [scan-build-py] Increase precision of timestamp in report directory name · 5fbaf12b
      Devin Coughlin authored
      This commit improves compatibility with the perl version of scan-build.
      
      The perl version of scan-build produces output report directories with
      increasing lexicographic ordering. This ordering is relied on by the CmpRuns.py
      tool in utils/analyzer when comparing results for build commands with multiple
      steps. That tool tries to line up the output directory for each step between
      different runs of the analyzer based on the increasing directory name.
      
      The python version of scan-build uses file.mkdtemp() with a time stamp
      prefix to create report directories. The timestamp has a 1-second precision.
      This means that when analysis of a single build step takes less than a second
      the ordering property that CmpRuns.py expects will sometimes not hold,
      depending on the timing and the random suffix generated by mkdtemp(). Ultimately
      this causes CmpRuns to incorrectly correlate results from build steps and report
      spurious differences between runs.
      
      This commit increases the precision of the timestamp used in scan-build-py to
      the microsecond level. This approach still has the same underlying issue -- but
      in practice analysis of any build step is unlikely to take less than a
      millisecond.
      
      Differential Revision: https://reviews.llvm.org/D24163
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@280768 91177308-0d34-0410-b5e6-96231b3b80d8
      5fbaf12b
  7. Aug 01, 2016
  8. May 31, 2016
  9. Apr 19, 2016
  10. Feb 21, 2016
  11. Feb 18, 2016
  12. Feb 10, 2016
  13. Jan 26, 2016
  14. Jan 12, 2016
Loading