llvm-svn: 125726

lit/TestingConfig.py: Add the environment variable PRINTF_EXPONENT_DIGITS as workaround [PR6745] for mingw's tests. Danil Malyshev suggested this.

FIXME: It does not improve MSVC's issue.

[Danil Malyshev] Defining PRINTF_EXPONENT_DIGITS env is the suggested way to make MinGW ANSI/POSIX compatible. This is not only about the case we are discussing, but in general, I'd like to have explicitly defined compatibility mode for all the tests running on MinGW.

llvm-svn: 125725

Patch thanks to Zach Anderson.

llvm-svn: 125721

llvm-svn: 125711

llvm-svn: 125710

llvm-svn: 125709

llvm-svn: 125702

it swaps the LHS/RHS of a single binop.

llvm-svn: 125700

llvm-svn: 125681

other getNode() methods.  Radar 9002173.

llvm-svn: 125665

llvm-svn: 125663

llvm-svn: 125660

llvm-svn: 125659

llvm-svn: 125658

llvm-svn: 125651

the right thing and stop trying to copy it. Fixes PR8944.

llvm-svn: 125648

transformation if we can't legally create a build vector of the correct
type. Check that we can make the transformation first, and add a TODO to
refactor this code with similar cases.

Fixes: PR9223 and rdar://9000350
llvm-svn: 125631

llvm-svn: 125630

llvm-svn: 125629

llvm-svn: 125625

Some single precision VFP instructions may be executed on NEON pipeline, but not double precision ones.

llvm-svn: 125624

integer. Fixes PR9228!

llvm-svn: 125613

This is submitted by Joerg Sonnenberger and fixes his PR8685.

llvm-svn: 125595

This is necessary to avoid a crash in certain tangled situations where a kill
flag is first correctly moved to a merged instruction, and then needs to be
moved again:

  STR %R0, a...
  STR %R0<kill>, b...

First becomes:

  STR %R0, b...
  STM a, %R0<kill>, ...

and then:

  STM a, %R0, ...
  STM b, %R0<kill>, ...

We can now remove the kill flag from the merged STM when needed. 8960050.

llvm-svn: 125591

Ignore DBG_VALUE machine instructions while constructing instruction ranges based on location info. 
Machine instruction range consisting of only DBG_VALUE MIs only contributes consecutive labels in assembly output, which is harmless, and empty scope entry in DebugInfo, which confuses debugger tools.

llvm-svn: 125577

llvm-svn: 125574

llvm-svn: 125571

llvm-svn: 125567

llvm-svn: 125563

-Use the tablegen class name for the checker class name.
-Mark checker packages as hidden/not hidden.

llvm-svn: 125558

Fix 9216 - Endless loop in InstCombine pass.
The pattern "A&(A^B) -> A & ~B" recreated itself because ~B is
actually a xor -1.

llvm-svn: 125557

llvm-svn: 125552

llvm-svn: 125547

llvm-svn: 125546

llvm-svn: 125544

llvm-svn: 125543

llvm-svn: 125537

llvm-svn: 125536

llvm-svn: 125534

Simplify the spill weight calculation a bit by bypassing
getApproximateInstructionCount() and using LiveInterval::getSize() directly.
This changes the computed spill weights, but only by a constant factor in each
function. It should not affect how spill weights compare against each other, and
so it shouldn't affect code generation.

llvm-svn: 125530