- Jul 31, 2013
-
-
Eric Christopher authored
llvm-svn: 187456
-
- Jul 30, 2013
-
-
Eric Christopher authored
In limited testing this seems to work. Caveat emptor. llvm-svn: 187452
-
- Jul 29, 2013
-
-
Aaron Ballman authored
Re-application of 187310. Re-enabling warning C4275 for MSVC 11 and up, but not MSVC 10 since it is still required there. llvm-svn: 187354
-
- Jul 28, 2013
-
-
Aaron Ballman authored
llvm-svn: 187331
-
- Jul 27, 2013
-
-
Aaron Ballman authored
llvm-svn: 187310
-
Aaron Ballman authored
llvm-svn: 187293
-
Aaron Ballman authored
llvm-svn: 187279
-
Aaron Ballman authored
llvm-svn: 187252
-
- Jul 17, 2013
-
-
Duncan Sands authored
The issue is that CMAKE_BUILD_TYPE=RelWithDebInfo LLVM_ENABLE_ASSERTIONS=ON was not building with assertions enabled. (I was unable to find what in the LLVM source tree was adding -DNDEBUG to the build line in this case, so decided that it must be cmake itself that was adding it - this may depend on the cmake version). The fix treats any mode that is not Debug as being the same as Release for this purpose (previously it was being assumed that cmake would only add -DNDEBUG for Release and not for RelWithDebInfo or MinSizeRel). If other versions of cmake don't add -DNDEBUG for RelWithDebInfo then that's OK: with this change you just get a useless but harmless -UNDEBUG or -DNDEBUG. llvm-svn: 186499
-
- Jun 14, 2013
-
-
Rafael Espindola authored
This reverts commit 183995. It broke the bots: http://bb.pgr.jp/builders/cmake-clang-x86_64-linux/builds/9730/steps/build_clang/logs/stdio llvm-svn: 183997
-
Arnaud A. de Grandmaison authored
llvm-svn: 183995
-
- May 29, 2013
-
-
Arnaud A. de Grandmaison authored
When invoked from Ninja, clang does not detect that it can use colors : see https://github.com/martine/ninja/issues/174 llvm-svn: 182878
-
- Apr 12, 2013
-
-
Alexey Samsonov authored
llvm-svn: 179367
-
- Apr 07, 2013
-
-
Reid Kleckner authored
MSVC 2012 gives warning D9025, "overriding /D NDEBUG with -UNDEBUG". Removing the original definition of NDEBUG silences this. llvm-svn: 178967
-
- Mar 26, 2013
-
-
Alexey Samsonov authored
Add CMake option LLVM_USE_SANITIZER={Address,Memory,MemoryWithOrigins} to simplify bootstrap of LLVM/Clang under ASan/MSan llvm-svn: 177992
-
- Mar 25, 2013
-
-
Duncan Sands authored
to have them appear in the right order. Instead append all warnings explicitly to the language flags. This was already the case for many warnings. Fixes the issue of -Wno-maybe-uninitialized not being effective because -Wall was being placed after it rather than before. llvm-svn: 177866
-
- Mar 19, 2013
-
-
Alexey Samsonov authored
llvm-svn: 177385
-
- Mar 15, 2013
-
-
Eric Christopher authored
issues. llvm-svn: 177136
-
- Mar 13, 2013
-
-
Alexey Samsonov authored
Summary: No functionality change. Reviewers: Bigcheese Reviewed By: Bigcheese CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D535 llvm-svn: 176973
-
- Mar 02, 2013
-
-
Jordan Rose authored
Previously we relied on it being included by config-ix.cmake. llvm-svn: 176396
-
- Feb 04, 2013
-
-
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
-
- Jan 31, 2013
-
-
Richard Smith authored
catches uses of an extremely minor and widely-available C++ extension (which every C++ compiler I could find supports, but EDG and Clang reject in strict mode). The diagnosed code pattern looks like this: struct X { union { struct { int a; int b; } S; }; }; llvm-svn: 174103
-
Edwin Vane authored
gcc produces false positives for empty braces so turning the warning off. Instead, turning the warning on for clang so proper warnings aren't missed. Reviewers: dblaikie, chandlerc llvm-svn: 174073
-
- Jan 27, 2013
-
-
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
-
- Jan 25, 2013
-
-
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
-
- Jan 03, 2013
-
-
Michael J. Spencer authored
llvm-svn: 171430
-
- Dec 24, 2012
-
-
Dmitri Gribenko authored
Now we really pass -Wcovered-switch-default if the compiler supports it. llvm-svn: 171040
-
- Nov 26, 2012
-
-
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
-
- Jun 08, 2012
-
-
Tobias Grosser authored
This was previously only done for executables and shared libraries, but not for modules. As modules are essentially shared libraries (that need to be dlopened explicitly), threating them the same as shared libraries seems reasonable. This fixes the LLVM_BUILD_32_BITS build of Polly. Contributed by: Ondra Hosek <ondra.hosek@gmail.com> llvm-svn: 158195
-
Michael J. Spencer authored
llvm-svn: 158176
-
- Jun 07, 2012
-
-
Michael J. Spencer authored
llvm-svn: 158171
-
Michael J. Spencer authored
Remove /Wall from LLVM_ENABLE_WARNINGS (it's useless) and promote 4239 to a level 1 warning. llvm-svn: 158170
-
- May 23, 2012
-
-
Tim Northover authored
llvm-svn: 157337
-
- May 08, 2012
-
-
Rafael Espindola authored
output. Peter Collingbourne also reports that it is showing up in $(llvm-config --cflags). Revert this for now since I don't know enough cmake to fix it properly. This reverts commit 18efed7adc79c1970f307bb5b015d199012ba872. llvm-svn: 156392
-
- May 04, 2012
-
-
Rafael Espindola authored
using cmake+ninja, since ninja buffers the compiler output. llvm-svn: 156150
-
- Apr 21, 2012
-
-
NAKAMURA Takumi authored
llvm-svn: 155285
-
NAKAMURA Takumi authored
llvm-svn: 155284
-
- Mar 01, 2012
-
-
Michael J. Spencer authored
llvm-svn: 151849
-
- Feb 29, 2012
-
-
Rafael Espindola authored
sure we don't use it with compilers that don't support it. llvm-svn: 151665
-
- Feb 28, 2012
-
-
Chandler Carruth authored
Clang builds. The detection logic for compilers that support the warning isn't working. Rafael is going to investigate it, but didn't want people to have to wade through build spam until then. llvm-svn: 151649
-