llvm-svn: 93150

The old test case has a little mistake.

llvm-svn: 93148

This with previous patch fixes a OSAtomic test case.

llvm-svn: 93146

llvm-svn: 93141

value bindings.  Along with a small change to OSAtomicChecker, this
resolves <rdar://problem/7527292> and resolves some long-standing
issues with how values can be bound to the same physical address by
not have the same "key".  This change is only a beginning; logically
RegionStore needs to better handle loads from addresses where the
stored value is larger/smaller/different type than the loaded value.
We handle these cases in an approximate fashion now (via
CastRetrievedVal and help in SimpleSValuator), but it could be made
much smarter.

llvm-svn: 93137

(1) Introduce a new 'BindingKey' class to match 'BindingValue'.  This
gives us the flexibility to change the current key value from 'const
MemRegion*' to something more interesting.

(2) Rework additions/removals/lookups from the store to use new
'Remove', 'Add', 'Lookup' utility methods.

No "real" functionality change; just prep work and abstraction.

llvm-svn: 93136

incompatible with user-defined literals, specifically with the following form:

  0x1p+1

The preprocessing-number token extends only as far as the 'p'; the '+' is not
included. Previously we could get away with this extension as p was an invalid
suffix, but now with user-defined literals, 'p' might well be a valid suffix
and we are forced to consider it as such.

This patch also adds a warning in non-0x C++ modes telling the user that
this extension is incompatible with C++0x that is enabled by default
(previously and with other languages, we warn only with a compliance
option such as -pedantic).

llvm-svn: 93135

C++ grammatical constructs that show up in top-level (namespace-level)
declarations, member declarations, template declarations, statements,
expressions, conditions, etc. For example, we now provide a pattern
for

  static_cast<type>(expr)

when we can have an expression, or

  using namespace identifier;

when we can have a using directive.

Also, improves the results of code completion at the beginning of a
top-level declaration. Previously, we would see value names (function
names, global variables, etc.); now we see types, namespace names,
etc., but no values.

llvm-svn: 93134

llvm-svn: 93133

RewriteObjC.cpp(4419) : warning C4804: '>' : unsafe use of type 'bool' in operation

llvm-svn: 93124

llvm-svn: 93120

llvm-svn: 93119

 1. Add helper class for sema checks for target attributes
 2. Add helper class for codegen of target attributes

As a proof-of-concept - implement msp430's 'interrupt' attribute.

llvm-svn: 93118

llvm-svn: 93117

llvm-svn: 93114

llvm-svn: 93101

nicer than passing around two const char*'s.

llvm-svn: 93094

llvm-svn: 93090

llvm-svn: 93088

llvm-svn: 93087

-weak_reference_mismatches is not present, it is the default.

llvm-svn: 93086

llvm-svn: 93085

llvm-svn: 93084

import other headers within the same framework with the full
framework path, not with a relative include.

llvm-svn: 93083

CallExpr/ObjCMessageExpr can be visited in an "lvalue" context if it
returns a struct temporary.  Currently the analyzer doesn't reason
about struct temporary returned by function calls, but we shouldn't
crash here either.

llvm-svn: 93081

llvm-svn: 93078

llvm-svn: 93077

llvm-svn: 93076

lvalue to poke, no functionality change.

llvm-svn: 93075

llvm-svn: 93074

rdar://7083878

llvm-svn: 93073

llvm-svn: 93072

llvm-svn: 93071

llvm-svn: 93064

llvm-svn: 93063

llvm-svn: 93060

llvm-svn: 93058

llvm-svn: 93057

std::vectors.

- MacroBuilder wraps a raw_ostream so it can easily write to any buffer
  supported by raw_ostream.
- MacroBuilder's method take Twines for easy string concatenation (this was done
  with sprintf and temporary buffers before).
- Targets still use std::vector as they don't have access to the builder.

llvm-svn: 93051

llvm-svn: 93049