Skip to content
  1. Apr 12, 2013
  2. Apr 07, 2013
  3. Mar 26, 2013
  4. Mar 25, 2013
  5. Mar 19, 2013
  6. Mar 15, 2013
  7. Mar 13, 2013
  8. Mar 02, 2013
  9. Feb 04, 2013
    • Edwin Vane's avatar
      Turn off uninitialized-use warnings for gcc in cmake build · a9c5bb3f
      Edwin Vane authored
      Added support to the cmake build to turn off uninitialized use warnings
      for gcc. This cleans the build up somewhat.
      
      Used logic simpler than found in autoconf by making use of the fact that
      although gcc won't complain about unsupported -Wno-* flags it *will*
      complain about unsupported -W flags.
      
      Reviewers: gribozavr, doug.gregor, chandlerc
      llvm-svn: 174299
      a9c5bb3f
  10. Jan 31, 2013
  11. Jan 27, 2013
    • NAKAMURA Takumi's avatar
      [CMake][Lit][unittests] Deprecate CMAKE_BUILD_TYPE in each build directory for unittests. · 61a8f974
      NAKAMURA Takumi authored
      For example,
      cur) unittests/ADT/Release/ADTTests
      new) unittests/ADT/ADTTests
      
      RUNTIME_BUILD_MODE can be substituted to CMAKE_CFG_INTDIR.
      
      With Make and Ninja, the tree is not built with multiple configurations.
      Then, including the build type in target directory doesn't make sense.
      See also "How can I build multiple modes without switching?"
      http://www.cmake.org/Wiki/CMake_FAQ
      CMAKE_CFG_INTDIR is set to "."
      
      With multiple-configuration-aware build system, like Visual Studio, each unittest is built on appropriate directory, for example,
      unittests/ADT/Release/ADTTests.exe
      CMAKE_CFG_INTDIR is set to build system's variable, like "$(Configuration)" or "$(OutDir)".
      
      Thus, "--param build_config" is also deprecated.
      
      llvm-svn: 173616
      61a8f974
  12. Jan 25, 2013
    • Reid Kleckner's avatar
      Disable MSVC's warning about noreturn destructors · cd947f97
      Reid Kleckner authored
      This warning fires on:
        Operator::~Operator() {
          llvm_unreachable("should never destroy an Operator");
        }
      
      That seems like a false positive.  I don't see any good way to silence
      the warning here, so I'm disabling it.
      
      llvm-svn: 173455
      cd947f97
  13. Jan 03, 2013
  14. Dec 24, 2012
  15. Nov 26, 2012
    • Joe Abbey's avatar
      Removing SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG · 15d9834d
      Joe Abbey authored
      Adding CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
             C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
      
      This is to handle the wackiness on a Mac host where cmake detects:
      
      CMAKE_CXX_COMPILER == "/usr/bin/c++"
      CMAKE_C_COMPILER == "/usr/bin/gcc"
      
      llvm-svn: 168577
      15d9834d
  16. Jun 08, 2012
  17. Jun 07, 2012
  18. May 23, 2012
  19. May 08, 2012
  20. May 04, 2012
  21. Apr 21, 2012
  22. Mar 01, 2012
  23. Feb 29, 2012
  24. Feb 28, 2012
  25. Jan 25, 2012
  26. Jan 20, 2012
  27. Dec 16, 2011
  28. Nov 04, 2011
  29. Oct 11, 2011
  30. Aug 17, 2011
  31. Jun 23, 2011
    • Andrew Trick's avatar
      lit support for REQUIRES: asserts. · 67ff0718
      Andrew Trick authored
      Take #2. Don't piggyback on the existing config.build_mode. Instead,
      define a new lit feature for each build feature we need (currently
      just "asserts"). Teach both autoconf'd and cmake'd Makefiles to define
      this feature within test/lit.site.cfg. This doesn't require any lit
      harness changes and should be more robust across build systems.
      
      llvm-svn: 133664
      67ff0718
  32. Jun 17, 2011
  33. May 11, 2011
Loading