Skip to content
Snippets Groups Projects
  1. Feb 11, 2016
  2. Feb 09, 2016
  3. Jan 26, 2016
  4. Sep 17, 2015
  5. Jun 23, 2015
  6. Jun 22, 2015
  7. May 17, 2015
    • Nico Weber's avatar
      Don't leak TemplateIds when a plugin parses late-parsed templates at TU end. · acb8cdf0
      Nico Weber authored
      In -fdelayed-template-parsing mode, templates that aren't used are not parsed
      at all.  For some diagnostic plugins, this is a problem since they want to
      analyse the contents of the template function body.  What has been suggested
      on cfe-dev [1] is to explicitly parse interesting templates in
      HandleTranslationUnit(); IWYU does this for example [2].
      
      This is workable, but since the delayed parsing doesn't run below a call to
      ParseTopLevelDecl(), no DestroyTemplateIdAnnotationsRAIIObj object is on the
      stack to clean up TemplateIds that are created during parsing.  To fix this,
      let ~Parser() clean them up in delayed template parsing mode instead of
      leaking (or asserting in +Assert builds).
      
      (r219810, relanded in r220400, fixed the same problem in incremental processing
      mode; the review thread of r219810 has a good discussion of the problem.)
      
      To test this, give the PrintFunctionNames plugin a flag to force parsing
      of a template and add a test that uses it in -fdelayed-template-parsing mode.
      Without the Parser.cpp change, that test asserts.
      
      1: http://lists.cs.uiuc.edu/pipermail/cfe-dev/2014-August/038415.html
      2: https://code.google.com/p/include-what-you-use/source/detail?r=566 
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@237531 91177308-0d34-0410-b5e6-96231b3b80d8
      acb8cdf0
  8. Apr 11, 2015
  9. Jan 23, 2015
  10. Oct 03, 2014
  11. Sep 04, 2014
  12. Sep 03, 2014
  13. Aug 19, 2014
  14. Aug 10, 2014
  15. Aug 08, 2014
  16. Aug 07, 2014
  17. Jul 24, 2014
  18. Jul 18, 2014
  19. Jul 17, 2014
  20. Jul 16, 2014
    • Alp Toker's avatar
      Make clang's rewrite engine a core feature · 6c4abb16
      Alp Toker authored
      The rewrite facility's footprint is small so it's not worth going to these
      lengths to support disabling at configure time, particularly since key compiler
      features now depend on it.
      
      Meanwhile the Objective-C rewriters have been moved under the
      ENABLE_CLANG_ARCMT umbrella for now as they're comparatively heavy and still
      potentially worth excluding from lightweight builds.
      
      Tests are now passing with any combination of feature flags. The flags
      historically haven't been tested by LLVM's build servers so caveat emptor.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@213171 91177308-0d34-0410-b5e6-96231b3b80d8
      6c4abb16
  21. Jul 15, 2014
  22. Jul 13, 2014
  23. Jul 11, 2014
  24. Jul 09, 2014
  25. Jul 01, 2014
  26. May 16, 2014
  27. Mar 09, 2014
  28. Feb 21, 2014
    • NAKAMURA Takumi's avatar
      [CMake] Get rid of explicit dependencies to include/clang/*.inc and introduce... · 0eed94f6
      NAKAMURA Takumi authored
      [CMake] Get rid of explicit dependencies to include/clang/*.inc and introduce CLANG_TABLEGEN_TARGETS.
      
      This does;
        - clang_tablegen() adds each tblgen'd target to global property CLANG_TABLEGEN_TARGETS as list.
        - List of targets is added to LLVM_COMMON_DEPENDS.
        - all clang libraries and targets depend on generated headers.
      
      You might wonder this would be regression, but in fact, this is little loss.
        - Almost all of clang libraries depend on tblgen'd files and clang-tblgen.
        - clang-tblgen may cause short stall-out but doesn't cause unconditional rebuild.
        - Each library's dependencies to tblgen'd files might vary along headers' structure.
          It made hard to track and update *really optimal* dependencies.
      
      Each dependency to intrinsics_gen and ClangSACheckers is left as DEPENDS.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@201842 91177308-0d34-0410-b5e6-96231b3b80d8
      0eed94f6
  29. Feb 20, 2014
    • Jordan Rose's avatar
      [CMake] Fix installation without CLANG_BUILD_EXAMPLES · dac75e7a
      Jordan Rose authored
      When CLANG_BUILD_EXAMPLES is not on we set the EXCLUDE_FROM_ALL
      directory property for the examples/ directory to tell CMake not to
      build them by default.  The AddLLVM.cmake APIs are not aware of this and
      try to install targets that are not built.  This does not cause an
      install-time error because CMake excludes the directory from the default
      installation.  However, now that installation attaches targets to the
      LLVMExports export set CMake-based applications that find_package(LLVM)
      fail because the example plugin binary is not available.
      
      Tell the AddLLVM.cmake APIs to exclude the examples from installation by
      setting the EXCLUDE_FROM_ALL variable they check.
      
      Patch by Brad King!
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@201799 91177308-0d34-0410-b5e6-96231b3b80d8
      dac75e7a
  30. Feb 13, 2014
Loading