earlier. Implicit bool -> int conversions are evil!

llvm-svn: 118651

llvm-svn: 118650

llvm-svn: 118649

llvm-svn: 118648

bitfield assignment.

Implements rdar://problem/7809123

llvm-svn: 118647

invoke the test driver to rerun the very same test.  Example output:

/Volumes/data/lldb/svn/trunk/test $ tail 2010-11-09-14_51_34/ExpectedFailure-TestSettings.SettingsCommandTestCase.test_set_output_path.log 

Traceback (most recent call last):
  File "/Volumes/data/lldb/svn/trunk/test/settings/TestSettings.py", line 136, in test_set_output_path
    "'stdout.txt' exists due to target.process.output-path.")
AssertionError: False is not True : 'stdout.txt' exists due to target.process.output-path.


To rerun this test, issue the following command from the 'test' directory:

./dotest.py -v -t -f SettingsCommandTestCase.test_set_output_path

llvm-svn: 118646

llvm-svn: 118645

llvm-svn: 118644

as derived from the target triple.  This is important for enabling
features that are implied based on the architecture version.

llvm-svn: 118643

It is only supported for ARM code.  Normally Thumb2 code would use DMB instead,
but depending on how the compiler is invoked (e.g., -mattr=-db) that might be
disabled.  This prevents a "cannot select MEMBARRIER_MCR" error in that
situation.  Radar 8644195

llvm-svn: 118642

llvm-svn: 118641

* LDM, et al, uses a bit mask to indicate the register list.
* VLDM, et al, uses a base register plus number.

The LDM instructions may be non-contiguous, but the VLDM ones must be
contiguous. Those are semantic checks that should be done later in the
compiler. Also postpone the creation of the bit mask until it's needed.

llvm-svn: 118640

llvm-svn: 118639

in the type copy routine to make type problems
easier to debug.

llvm-svn: 118638

own subcategory, -Wconstant-conversion, which is on by default.

Tweak the constant folder to give better results in the invalid
case of a negative shift amount.

Implements rdar://problem/6792488

llvm-svn: 118636

llvm-svn: 118635

// rdar://8632525

llvm-svn: 118634

help in MC'izing the references that use them.

llvm-svn: 118633

    @unittest2.skip("rdar://problem/8641483 ./dotest.py -v -t -w forward seg faults")

and add a @skip decorator for test_with_dwarf_and_run_command() method:

    @unittest2.skip("rdar://problem/8648070 'expression *bar_ptr' seg faults")

llvm-svn: 118632

conditional operators. Fixes PR7863.

llvm-svn: 118631

(retry now that the windows build is green)

llvm-svn: 118630

// rdar://8283484

llvm-svn: 118629

llvm-svn: 118628

llvm-svn: 118627

llvm-svn: 118626

llvm-svn: 118625

memory. This isn't a real improvement with present day AliasAnalysis
implementations; it's mainly for consistency.

llvm-svn: 118624

llvm-svn: 118623

llvm-svn: 118622

llvm-svn: 118621

That bug concerned the well-formedness of code such as (&ovl)(a, b,
c). GCC rejects the code, while EDG accepts it. On further study of the
standard, I see no support for EDG's position: in particular, C++
[over.over] does not list this as a context where we can take the
address of an overloaded function, C++ [over.call.func] does not
reference the address-of operator at any point, and C++ [expr.call]
claims that the function argument in a call is either a function
lvalue or a pointer-to-function; (&ovl) is neither.

llvm-svn: 118620

llvm-svn: 118619

llvm-svn: 118618

llvm-svn: 118617

-Wnon-virtual-dtor.

llvm-svn: 118616

llvm-svn: 118615

property IntrReadArgMem can be modeled.

llvm-svn: 118614

llvm-svn: 118613

make the example a bit better, encouraging people to use "suggestions of what to use" in the message :)

llvm-svn: 118612

llvm-svn: 118611