- 22 Jul, 2014 8 commits
-
-
Bill Wendling authored
llvm-svn: 213607 llvm-svn: 213606 llvm-svn: 213605 llvm-svn: 213604 llvm-svn: 213603 llvm-svn: 213602 llvm-svn: 213601 llvm-svn: 213598 llvm-svn: 213597
-
Richard Smith authored
file not in the test/ area). Backing out now so that this test isn't part of the 3.5 branch. Original commit message: "TableGen: Allow AddedComplexity values to be negative [...]" llvm-svn: 213596
-
Saleem Abdulrasool authored
Windows ARM indicates __va_start as a variadic function. However, the function itself is treated as having 4 formal arguments: - (out) pointer to the va_list - (in) address of the last named argument - (in) slot size for the type of the last argument - address of the last named argument The last argument does not seem to have any bearing on codegen, and thus is not explicitly type checked at this point. Unlike the previous handling for __va_start, it does not currently validate if the parameter is the last named parameter (it seems that MSVC currently accepts this). llvm-svn: 213595
-
Serge Pavlov authored
If function parameters have default values, and that of the second parameter is parsed with errors, function declaration would have a parameter without default value that follows a parameter with that. Such declaration breaks logic of selecting overloaded function. As a solution, put opaque object as default value in such case. This patch fixes PR20055. Differential Revision: http://reviews.llvm.org/D4378 llvm-svn: 213594
-
Reid Kleckner authored
Summary: This pragma is very rare. We could *hypothetically* lower some uses of it down to @llvm.global_ctors, but given that GlobalOpt isn't able to optimize prioritized global ctors today, there's really no point. If we wanted to do this in the future, I would check if the section used in the pragma started with ".CRT$XC" and had up to two characters after it. Those two characters could form the 16-bit initialization priority that we support in @llvm.global_ctors. We would have to teach LLVM to lower prioritized global ctors on COFF as well. This should let us compile some silly uses of this pragma in WebKit / Blink. Reviewers: rsmith, majnemer Subscribers: cfe-commits Differential Revision: http://reviews.llvm.org/D4549 llvm-svn: 213593
-
Nick Kledzik authored
llvm-svn: 213592
-
Kate Stone authored
1) Preserve ref qualification state in a local variable while parsing a nested name. Previously, the state was recorded in the shared db reference and could therefore be overwritten when parsing multiple levels of nested names (e.g.: when a qualified name has qualified template args.) 2) Address an off-by-one error when testing whether or not a thunk is non-virtual. This resulted in the demangled identifying all thunks as non-virtual. llvm-svn: 213591
-
Alexey Samsonov authored
llvm-svn: 213590
-
- 21 Jul, 2014 32 commits
-
-
Hans Wennborg authored
Both /showIncludes and /E write to stdout. Allowing both results in interleaved output and an error when double-closing the file descriptor, intended to catch issues like this. llvm-svn: 213589
-
Mark Heffernan authored
llvm-svn: 213588
-
Mark Heffernan authored
llvm-svn: 213587
-
Eli Bendersky authored
llvm-svn: 213586
-
Nick Kledzik authored
Over time the symbols and relocations have changed for dwarf unwind info in the __eh_frame section. Add test cases for older and new style. llvm-svn: 213585
-
Hans Wennborg authored
Previously it was hard-coded to 1.0, which meant the installer would not install the plugin over previous versions. This commit makes us use LLVM's major.minor.patch version from cmake, or whatever CLANG_FORMAT_VS_VERSION is set to when configuring the build. It's pretty dirty to update a configuration file in the source directory from the cmake build like this. However, the plugin build is already dirty in this regard since it builds in the source dir when visual studio, and then copies out the resulting vsix. llvm-svn: 213584
-
Alexey Samsonov authored
llvm-svn: 213583
-
Hal Finkel authored
As it turns out, the capture tracker named CaptureBefore used by AA, and now available via the PointerMayBeCapturedBefore function, would have been more-aptly named CapturedBeforeOrAt, because it considers captures at the instruction provided. This is not always what one wants, and it is difficult to get the strictly-before behavior given only the current interface. This adds an additional parameter which controls whether or not you want to include captures at the provided instruction. The default is not to include the instruction provided, so that 'Before' matches its name. No functionality change intended. llvm-svn: 213582
-
David Blaikie authored
Revert "Recommit r212203: Don't try to construct debug LexicalScopes hierarchy for functions that do not have top level debug information." This reverts commit r212649 while I investigate/reduce/etc PR20367. llvm-svn: 213581
-
Tom Stellard authored
llvm-svn: 213580
-
Arnaud A. de Grandmaison authored
This commit did break the sanitizer-x86 bot. Revert it while investigating. llvm-svn: 213579
-
Mark Heffernan authored
llvm-svn: 213578
-
Alexey Samsonov authored
llvm-svn: 213577
-
Arnaud A. de Grandmaison authored
This will give more information to the optimizers so that they can reuse stack slots. llvm-svn: 213576
-
Saleem Abdulrasool authored
LLDWrapPython.cpp is a generated file. This contains a double assignment to the same value, which causes GCC to emit a warning about sequence point evaluation causing a use-before-init. Simply silence the warning. llvm-svn: 213575
-
Mark Heffernan authored
llvm-svn: 213574
-
Justin Bogner authored
This fixes a couple of asserts when analyzing comparisons involving C11 atomics that were uncovered by r205608 when we extended the applicability of -Wtautological-constant-out-of-range-compare. llvm-svn: 213573
-
Saleem Abdulrasool authored
GCC believes it may be possible to not return a value from the switch: lib/Target/R600/SIRegisterInfo.cpp:187:1: warning: control reaches end of non-void function [-Wreturn-type] Add an unreachable label to indicate that this is not possible and still permit switch coverage checking. llvm-svn: 213572
-
Tom Stellard authored
llvm-svn: 213571
-
Tom Stellard authored
llvm-svn: 213570
-
Logan Chien authored
We should update the usages to all of the results; otherwise, we might get assertion failure or SEGV during the type legalization of ATOMIC_CMP_SWAP_WITH_SUCCESS with two or more illegal types. For example, in the following sequence, both i8 and i1 might be illegal in some target, e.g. armv5, mipsel, mips64el, %0 = cmpxchg i8* %ptr, i8 %desire, i8 %new monotonic monotonic %1 = extractvalue { i8, i1 } %0, 1 Since both i8 and i1 should be legalized, the corresponding ATOMIC_CMP_SWAP_WITH_SUCCESS dag will be checked/replaced/updated twice. If we don't update the usage to *ALL* of the results in the first round, the DAG for extractvalue might be processed earlier. The GetPromotedInteger() will result in assertion failure, because its operand (i.e. the success bit of cmpxchg) is not promoted beforehand. llvm-svn: 213569 -
Deepak Panickal authored
llvm-svn: 213568
-
Deepak Panickal authored
llvm-svn: 213567
-
Deepak Panickal authored
llvm-svn: 213566
-
Deepak Panickal authored
llvm-svn: 213565
-
Tom Stellard authored
llvm-svn: 213564
-
Tom Stellard authored
llvm-svn: 213563
-
Duncan P. N. Exon Smith authored
This reverts commit r213474 (and r213475), which causes a miscompile on a stage2 LTO build. I'll reply on the list in a moment. llvm-svn: 213562
-
Tom Stellard authored
This pass converts 64-bit instructions to 32-bit when possible. llvm-svn: 213561
-
David Blaikie authored
llvm-svn: 213560
-
Dan Liew authored
llvm-svn: 213559
-
Tom Stellard authored
Therefore we don't need to add it to the implict defs list. llvm-svn: 213558
-