Vector compare using altivec 'vcmpxxx' instructions have as third argument
a vector register instead of CR one, different from integer and float-point
compares. This leads to a failure in code generation, where 'SelectSETCC'
expects a DAG with a CR register and gets vector register instead.

This patch changes the behavior by just returning a DAG with the 
vector compare instruction based on the type. The patch also adds a testcase
for all vector types llvm defines.

It also included a fix on signed 5-bits predicates printing, where
signed values were not handled correctly as signed (char are unsigned by
default for PowerPC). This generates 'vspltisw' (vector splat)
instruction with SIM out of range.

llvm-svn: 165419

llvm-svn: 165418

llvm-svn: 165417

llvm-svn: 165416

llvm-svn: 165411

This patch add altivec support for v4i32 to v4f32 and for v4f32 to
v4i32 vector rounding conversion.

llvm-svn: 165409

llvm-svn: 165406

llvm-svn: 165404

llvm-svn: 165403

llvm-svn: 165402

llvm-svn: 165401

Some regression tests which are testing the old jit and are exercising functionality which is both known to be broken and not expected to be fixed in the old jit. To remove these from the regression test output, I've marked them XFAIL (for lit tests) and ifdef'd them out (unit tests). These modifications remove the last long-standing regression test failures from the buildbots (though updating the triple to reflect new ubuntu configuration has temporarily caused some new failures). Tested on x86-64 and ARM Linux.

Patch by David Tweed!

llvm-svn: 165390

llvm-svn: 165382

llvm-svn: 165381

Found the fix on this page:
http://permalink.gmane.org/gmane.comp.python.sphinx.devel/112

llvm-svn: 165380

Otherwise it will try to use SSE patterns and fail horribly if sse is disabled.
Fixes PR14035.

llvm-svn: 165377

contents of the Attributes class over to an AttributesImpl.

llvm-svn: 165373

llvm-svn: 165372

llvm-svn: 165371

llvm-svn: 165369

Without this change, when the estimated cost for inlining a function with
an "alwaysinline" attribute was lower than the inlining threshold, the
getInlineCost function was returning that estimated cost rather than the
special InlineCost::AlwaysInlineCost value. That is fine in the normal
inlining case, but it can fail when the inliner considers the opportunity
cost of inlining into an internal or linkonce-odr function. It may decide
not to inline the always-inline function in that case. The fix here is just
to make getInlineCost always return the special value for always-inline
functions. I ran into this building clang with libc++. Tablegen failed to
link because of an always-inline function that was not inlined. I have been
unable to reduce the testcase down to a reasonable size.

llvm-svn: 165367

llvm-svn: 165366

move from and to coprocessors 0 and 2.

Contributer: Vladimir Medic
llvm-svn: 165351

Contributer: Vladimir Medic
llvm-svn: 165350

Contributer: Vladimir Medic
llvm-svn: 165346

into separate versions for the Darwin and 64-bit SVR4 ABIs.  This will
facilitate doing more major surgery on the 64-bit SVR4 ABI in the near future.

llvm-svn: 165336

llvm-svn: 165335

llvm-svn: 165334

llvm-svn: 165331

llvm-svn: 165326

llvm-svn: 165324

llvm-svn: 165322

No functionality change.

llvm-svn: 165321

llvm-svn: 165320

llvm-svn: 165319

Implement TargetData with the DataLayout class, this will allow LLVM projects to transition to DataLayout without loosing functionality.

llvm-svn: 165318

llvm-svn: 165316

- Mark the BCC and BLR defs as isCodeGenOnly per error output from
llvm-tblgen -gen-asm-matcher.

 PPCInstrInfo.td |   11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

llvm-svn: 165315

llvm-svn: 165314

llvm-svn: 165313