options, to enable easier testing of the innards of LLVM that are
enabled by such optimization strategies.

Note that this doesn't provide the (much needed) function attribute
support for -Oz (as opposed to -Os), but still seems like a positive
step to better test the logic that Clang currently relies on.

Patch by Patrik Hägglund.

llvm-svn: 156913

llvm-svn: 156912

on Linux in the getting started documentation.

Patch by Nathan Ridge.

llvm-svn: 156911

llvm-svn: 156910

llvm-svn: 156909

llvm-svn: 156908

llvm-svn: 156907

[tsan] add  ThreadSanitizer linker flags on Linux and also copy the tsan-rt into the appropriate place at build time

llvm-svn: 156906

generated code (for Intrinsic::getType) into a table.  This handles common cases right now,
but I plan to extend it to handle all cases and merge in type verification logic as well
in follow-on patches.

llvm-svn: 156905

llvm-svn: 156904

llvm-svn: 156902

This improves the conversion diagnostics (by correctly pointing to the loop
construct for conversions that may've been caused by the contextual conversion
to bool caused by a condition expression) and also causes the NULL conversion
warnings to be correctly suppressed when crossing a macro boundary in such a
context. (previously, since the conversion context location was incorrect, the
suppression could not be performed)

Reported by Nico Weber as feedback to r156826.

llvm-svn: 156901

Make sure that our thread list can't get out of date like was happening before Jims fix in revision 156894.

llvm-svn: 156898

Fixes pr12835.

llvm-svn: 156897

llvm-svn: 156896

Always call RefreshStateAfterStop when we get a stop event.  We were skipping doing it in the case where we had interrupted the target.  Presumably at some point in the past RefreshStateAfterStop was done more directly when we handled the interrupt, but it isn't any more so now we need to do it all the time.

llvm-svn: 156894

llvm-svn: 156891

To do that, keep track of the location of the protocol id in the ObjCProtocolExpr
AST node.

rdar://11190837

llvm-svn: 156890

llvm-svn: 156888

llvm-svn: 156887

DataVisualization.h / DataVisualization.cpp / ValueObject.cpp
and
FormatManager.h / FormatManager.cpp

llvm-svn: 156886

llvm-svn: 156885

llvm-svn: 156884

<rdar://problem/10800927> 

llvm-svn: 156883

llvm-svn: 156882

llvm-svn: 156881

Part of rdar://11438360

llvm-svn: 156880

Make sure our debugger STDIN read thread shuts down quickly when we are done with it. We had a case where the owner of the file handle was not closing it and caused spins.

llvm-svn: 156879

It is now possible to coalesce weird skewed sub-register copies by
picking a super-register class larger than both original registers. The
included test case produces code like this:

  vld2.32 {d16, d17, d18, d19}, [r0]!
  vst2.32 {d18, d19, d20, d21}, [r0]

We still perform interference checking as if it were a normal full copy
join, so this is still quite conservative. In particular, the f1 and f2
functions in the included test case still have remaining copies because
of false interference.

llvm-svn: 156878

llvm-svn: 156876

llvm-svn: 156875

more liberal in rewriting when the parameter is an enum constant.

Part of rdar://11438360

llvm-svn: 156873

type and its accessor type and issue error if types
are incompatible, instead of crashing in IRgen.
// rdar://1105153

llvm-svn: 156871

We can no longer rely on children iterator to visit all the AST
tree children of an expression (OpaqueValueExpr has no children).

llvm-svn: 156870

It is possible to coalesce two overlapping registers to a common
super-register that it larger than both of the original registers.

The important difference is that it may be necessary to rewrite DstReg
operands as well as SrcReg operands because the sub-register index has
changed.

This behavior is still disabled by CoalescerPair.

llvm-svn: 156869

to use the @() boxing syntax.

It will also rewrite uses of stringWithCString:encoding: where the encoding that is
used is NSASCIIStringEncoding or NSUTF8StringEncoding.

rdar://11438360

llvm-svn: 156868

This can happen when widening a virtual register to a super-register
class.

llvm-svn: 156867

There is no need to look at an always null SrcIdx.

llvm-svn: 156866

 - Hopefully fixes PR11600 (untested).

llvm-svn: 156865

llvm-svn: 156864