- Jan 26, 2011
-
-
Jakob Stoklund Olesen authored
No functional change. llvm-svn: 124257
-
Jeffrey Yasskin authored
llvm-svn: 124256
-
Douglas Gregor authored
lvalues, nor can one take the address of an xvalue, by adding appropriate static_cast's (in the first case) and a temporary (in the second case). llvm-svn: 124255
-
Johnny Chen authored
Update emulate_sub_sp_imm to handle Encoding T1. llvm-svn: 124253
-
Howard Hinnant authored
llvm-svn: 124252
-
Greg Clayton authored
llvm-svn: 124251
-
Greg Clayton authored
llvm-svn: 124250
-
Argyrios Kyrtzidis authored
llvm-svn: 124249
-
Johnny Chen authored
Update emulate_sub_sp_imm to handle Encoding T2 & T3. llvm-svn: 124248
-
Douglas Gregor authored
llvm-svn: 124247
-
Devang Patel authored
llvm-svn: 124245
-
-
-
Argyrios Kyrtzidis authored
Change error "function cannot return array type" -> "blocks cannot return array type" when blocks are involved. Addresses rdar://8876238. llvm-svn: 124242
-
Douglas Gregor authored
workaround relied on rvalue references binding to non-function lvalues, while the original formulation (with std::forward) does the right thing. llvm-svn: 124241
-
Stephen Wilson authored
With the current target revision of Clang libclangChecker no longer exists and is not needed. Update the include path so we can get at ARM_DWARF_Registers.h and friends. llvm-svn: 124240
-
- Jan 25, 2011
-
-
Ted Kremenek authored
contents, with the additional warning flag (and still marked XFAIL). llvm-svn: 124239
-
Ted Kremenek authored
handling all CFGElement kinds. While writing the test case, it turned out that return-noreturn.cpp wasn't actually testing anything since it has the wrong -W flag. That uncovered another regression with the handling of destructors marked noreturn. WIP. llvm-svn: 124238
-
Johnny Chen authored
to an operation to adjust the stack pointer (allocate space for local storage). llvm-svn: 124237
-
Douglas Gregor authored
for reference binding (C++ [over.rank.ics]p3b1sb4), so that we prefer the binding of an lvalue reference to a function lvalue over the binding of an rvalue reference. This change resolves the ambiguity with std::forward and lvalue references to function types in a way that seems consistent with the original rvalue references proposal. My proposed wording for this change is shown in isBetterReferenceBindingKind(); we'll try to get this change adopted in the C++0x working paper as well. llvm-svn: 124236
-
Ted Kremenek authored
llvm-svn: 124235
-
David Greene authored
[AVX] Fix a typo in the extract subvector type constraints to specify the correct number of operands. llvm-svn: 124234
-
Bill Wendling authored
llvm-svn: 124233
-
Greg Clayton authored
Removed incorrect enumeration from switch. llvm-svn: 124232
-
Greg Clayton authored
Fixed bug reported by Ken Ryall. llvm-svn: 124231
-
Bill Wendling authored
appropriately so that it prints out the decimal representation. llvm-svn: 124230
-
Bill Wendling authored
encoding. It's up to the individual back-ends to convert it to their preferred representation when printing. llvm-svn: 124229
-
Ted Kremenek authored
about them yet. Fixes crash reported in PR 9049. llvm-svn: 124228
-
Nico Weber authored
llvm-svn: 124227
-
Jeffrey Yasskin authored
authors to write class __attribute__((forbid_temporaries)) Name { ... }; when they want to force users to name all variables of the type. This protects people from doing things like creating a scoped_lock that only lives for a single statement instead of an entire scope. The warning produced by this attribute can be disabled by -Wno-forbid-temporaries. llvm-svn: 124217
-
Douglas Gregor authored
(C++0x [over.ics.rank]p3) when one binding is an lvalue reference and the other is an rvalue reference that binds to an rvalue. In particular, we were using the predict "is an rvalue reference" rather than "is an rvalue reference that binds to an rvalue", which was incorrect in the one case where an rvalue reference can bind to an lvalue: function references. This particular issue cropped up with std::forward, where Clang was picking an std::forward overload while forwarding an (lvalue) reference to a function. However (and unfortunately!), the right answer for this code is that the call to std::forward is ambiguous. Clang now gets that right, but we need to revisit the std::forward implementation in libc++. llvm-svn: 124216
-
Ted Kremenek authored
by ExplodedNodes. This leads to about a 4-8% reduction in memory footprint when analyzing functions in sqlite3. llvm-svn: 124214
-
Ted Kremenek authored
about uninitialized variables captured by blocks. llvm-svn: 124213
-
Ted Kremenek authored
for a block capturing the value of an uninitialized variable. llvm-svn: 124212
-
Douglas Gregor authored
generate meaningful [*] template argument location information. [*] Well, as meaningful as possible, given that this entire code path is a hack for when we've lost type-source information. llvm-svn: 124211
-
Rafael Espindola authored
llvm-svn: 124210
-
Rafael Espindola authored
llvm-svn: 124209
-
Johnny Chen authored
llvm-svn: 124208
-
Douglas Gregor authored
llvm-svn: 124204
-
Devang Patel authored
Resolve DanglingDbgValue of PHI nodes where the use follows dbg.value intrinisic. llvm-svn: 124203
-