I've see cases where there are lingering processes ("hello_world") staying around and the
test_with_dsym_and_attach_to_process_with_name_api() test case just hangs.

llvm-svn: 148417

of recognizing them by name.

llvm-svn: 148416

llvm-svn: 148415

much smarter by extracting search results more efficiently and by properly obeying the 
must_be_implementation bool in the SymbolFileDWARF::FindCompleteObjCDefinitionTypeForDIE()
function.

llvm-svn: 148413

generational scheme for identifiers that avoids searching the hash
tables of a given module more than once for a given
identifier. Previously, loading any new module invalidated all of the
previous lookup results for all identifiers, causing us to perform the
lookups repeatedly.

llvm-svn: 148412

llvm-svn: 148411

into Lexer and Preprocessor; making it widely available.

llvm-svn: 148410

llvm-svn: 148408

in favor of usage of api's intended for.
// rdar://8290002

llvm-svn: 148404

Add a test case where 'settings set frame-format' supplies a format string containing, among other things, a single backtick character.

rdar://problem/10712130

llvm-svn: 148403

llvm-svn: 148401

llvm-svn: 148400

llvm-svn: 148399

llvm-svn: 148396

llvm-svn: 148394

also needs -fcxx-modules to enable modules for C++/Objective-C++.

llvm-svn: 148393

llvm-svn: 148392

llvm-svn: 148391

L'x' is actually wchar_t

support C11 u and U char literals

llvm-svn: 148390

Updates ProcessUCNExcape() for C++. C++11 allows UCNs in character
and string literals that represent control characters and basic
source characters. Also C++03 allows UCNs that refer to surrogate
codepoints.

UTF-8 sequences in character literals are now handled as single
c-chars.

Added error for multiple characters in Unicode character literals.

Added errors for when a the execution charset encoding of a c-char
cannot be represented as a single code unit in the associated
character type. Note that for the purposes of this error the asso-
ciated character type for a narrow character literal is char, not
int, even though in C narrow character literals have type int.

llvm-svn: 148389

llvm-svn: 148388

llvm-svn: 148387

llvm-svn: 148386

Implement AsanProcMaps for Mac OS. The code from sysinfo/ is not needed anymore and should be cleaned up.

llvm-svn: 148385

llvm-svn: 148384

Fix a bug in the type-legalization of vector integers. When we bitcast one vector type to another, we must not bitcast the result if one type is widened while the other is promoted.

llvm-svn: 148383

No new unit tests yet as there is no behavioral change
(except for slightly more specific filtering in
Sema::ActOnStartOfLambdaDefinition). Tests will be added
as the code paths are traced in greater depth to determine
how to improve the results--there are at least one or two
known bugs that require those improvements. This commit
lays the groundwork for those changes.

llvm-svn: 148382

for it to be used in converted constant expression checking, and fix a couple
of issues:
 - Conversion operators implicitly invoked prior to the narrowing conversion
   were not being correctly handled when determining whether a constant value
   was narrowed.
 - For conversions from floating-point to integral types, the diagnostic text
   incorrectly always claimed that the source expression was not a constant
   expression.

llvm-svn: 148381

llvm-svn: 148380

Add a '-X excluded-dir' option to the test driver to exclude a directory from consideration during test discovery.  For example:

    ./dotest.py -X types -v

from the test dir will ignore test cases under test/types.

llvm-svn: 148379

llvm-svn: 148378

Fix ISD::REG_SEQUENCE to accept physical registers and change TwoAddressInstructionPass to insert copies for any physical reg operands of the REG_SEQUENCE

llvm-svn: 148377

Make PotentiallyPotentiallyEvaluated contexts work correctly when referencing a class field from outside an instance method.

llvm-svn: 148376

llvm-svn: 148375

builtin.

llvm-svn: 148374

llvm-svn: 148373

TaintPropagationRule::process().

Also remove the "should be a pointer argument" warning - should be
handled elsewhere.

llvm-svn: 148372

size (Ex: in malloc, memcpy, strncpy..)

(Maybe some of this could migrate to the CString checker. One issue
with that is that we might want to separate security issues from
regular API misuse.)

llvm-svn: 148371

functions.

llvm-svn: 148370

llvm-svn: 148369