rdar://13318048

llvm-svn: 176828

An invoke may require a table entry. For instance, when the function it calls
is expected to throw.
<rdar://problem/13360379>

llvm-svn: 176827

This allows R600 Target to use the newly created -verify-misched llc flag

llvm-svn: 176819

llvm-svn: 176809

llvm-svn: 176808

In the spirit of r172109. Version control keeps a far more detailed
record of authorship anyways.

llvm-svn: 176807

llvm-svn: 176798

llvm-svn: 176797

llvm-svn: 176796

error above. Based on a patch by Peter Zotov!

llvm-svn: 176794

llvm-svn: 176793

After the recent data-structure improvements, a couple of debugging statements
were broken (printing pointer values).

llvm-svn: 176791

llvm-svn: 176787

llvm-svn: 176785

llvm-svn: 176784

llvm-svn: 176783

llvm-svn: 176782

Remove an unused member variable from HelpPrinter. Move another member variable to be a local variable in the only method that uses it.

llvm-svn: 176778

intrinsic - it can cause impossible-to-schedule subgraphs to be
introduced.

PR15053.

llvm-svn: 176777

llvm-svn: 176776

This made us emit runtime checks in a random order. Hopefully bootstrap
miscompares will go away now.

llvm-svn: 176775

llvm-svn: 176773

llvm-svn: 176772

llvm-svn: 176771

llvm-svn: 176770

Ignore all DbgIntriniscInfo instructions instead of just DbgValueInst.

llvm-svn: 176769

We want vectorization to happen at -g. Ignore calls to the dbg.value intrinsic
and don't transfer them to the vectorized code.

radar://13378964

llvm-svn: 176768

The strlen+memcmp was hidden in a call to StringRef::operator==. We check if
there are any null bytes in the string upfront so we can simplify the comparison
Small speedup when compiling code with many function calls.

llvm-svn: 176766

llvm-svn: 176765

r176751. Also, learn a lesson about applying patches by hand/eyeball.

llvm-svn: 176764

llvm-svn: 176763

for choosing to emit a shndx was simply testing the wrong variable.

llvm-svn: 176762

Count the subprograms, not the compile units.

llvm-svn: 176751

it. Fortunately, versions of gcov that predate the extra checksum also ignore
any extra data, so this isn't a problem. There will be a matching commit in
compiler-rt.

llvm-svn: 176745

PHIs are allowed to have multiple operand pairs per predecessor, and
this code works just fine when it happens.

llvm-svn: 176734

Summary:
Statistics are still available in Release+Asserts (any +Asserts builds),
and stats can also be turned on with LLVM_ENABLE_STATS.

Move some of the FastISel stats that were moved under DEBUG()
back out of DEBUG(), since stats are disabled across the board now.

Many tests depend on grepping "-stats" output.  Move those into
a orig_dir/Stats/. so that they can be marked as unsupported
when building without statistics.

Differential Revision: http://llvm-reviews.chandlerc.com/D486

llvm-svn: 176733

llvm-svn: 176729

llvm-svn: 176722

The getOperandPtr utility already bounds checks, but allows one-off-the-end.
This assert should catch the cases that could previously have been dereferencing
these one-off-the-end pointer. Happily, no cases of this came up with this
change.

llvm-svn: 176721

llvm-svn: 176720