llvm-svn: 141891

llvm-svn: 141887

Tweak -Wuninitialized's handling of 'int x = x' to report that as the root cause of an uninitialized variable IFF there are other uses of that uninitialized variable.  Fixes <rdar://problem/9259237>.

llvm-svn: 141881

llvm-svn: 141878

functions, e.g., (&f)(0). Fixes <rdar://problem/9803316>.

llvm-svn: 141877

Patch by Pekka Jääskeläinen!

llvm-svn: 141865

attributes are found, propagate them to subsequent declarations.

llvm-svn: 141861

Fix crash-on-invalid, improve error recovery, and test coverage for missing colon after access specifiers in C++

llvm-svn: 141852

llvm-svn: 141837

part of template argument deduction is ill-formed, we mark it as
invalid and treat it as a deduction failure. If we happen to find that
specialization again, treat it as a deduction failure rather than
silently building a call to the declaration.

Fixes PR11117, a marvelous bug where deduction failed after creating
an invalid specialization, causing overload resolution to pick a
different candidate. Then we performed a similar overload resolution
later, and happily picked the invalid specialization to
call... resulting in a silent link failure.

llvm-svn: 141809

llvm-svn: 141806

This changes clang to match GCC's behavior for __extension__, which temporarily
disables the -pedantic flag.  Warnings that are enabled without -pedantic
are not affected.  Besides the general goodness of matching GCC's precedent,
my motivation for this is that macros in the arm_neon.h header need to use
__extension__ to avoid pedantic complaints about their use of statement
expressions, yet we still want to warn about incompatible pointer arguments
for those macros.

llvm-svn: 141804

the same behavior of gcc by keeping the attribute out of the function type.

llvm-svn: 141803

Implement built-in macro '__has_warning', which allows one to query if a warning flag is valid.  Fixes <rdar://problem/10263428>.

llvm-svn: 141802

We'd also like for "C++11" or "c++11" to be used for the warning
groups, but without removing the old warning flags. Patches welcome;
I've run out of time to work on this today.

llvm-svn: 141801

llvm-svn: 141798

llvm-svn: 141796

llvm-svn: 141795

llvm-svn: 141793

fixes http://llvm.org/PR11120

llvm-svn: 141788

llvm-svn: 141785

delimiter pairs and detect when we exceed the implementation limit for
nesting depth, from Aaron Ballman!

llvm-svn: 141782

ignore access entirely for it) and not to crash on assignment operator
templates. Fixes PR11110.

llvm-svn: 141777

llvm-svn: 141773

Patch by Hal Finkel!

llvm-svn: 141772

taking into account macro arguments.

llvm-svn: 141771

llvm-svn: 141770

llvm-svn: 141769

The standard doesn't allow this, but mutable constexpr variables break the
semantics so badly that we can't reasonably accept them.

llvm-svn: 141768

if we're going to delete the setLocation as we did in 141732.

llvm-svn: 141762

swaps over the <<<< and >>>> markers, and uses shorter markers than traditional
tools.

llvm-svn: 141751

property in the diagnostic.

llvm-svn: 141745

and DefaultFunctionArrayLvalueConversion.  To prevent
significant regression for should-this-be-a-call fixits,
and to repair some such regression from the introduction of
bound member placeholders, make those placeholder checks
try to build calls appropriately.  Harden the build-a-call
logic while we're at it.

llvm-svn: 141738

to their fragile-abi representation.

llvm-svn: 141735

Migrate most of the location setting within the larger API in CGDebugInfo and
update a lot of callers.
Remove the existing file/scope change machinery in UpdateLineDirectiveRegion
and replace it with DILexicalBlockFile usage.

Finishes off the rest of rdar://10246360

llvm-svn: 141732

llvm-svn: 141731

llvm-svn: 141730

llvm-svn: 141723

llvm-svn: 141719

Constant expression evaluation: refactor value initialization and scalar list initialization into base class.

llvm-svn: 141717