When a call is placed to spill an interval this spiller will first try to
break the interval up into its component values. Single value intervals and
intervals which have already been split (or are the result of previous splits)
are spilled by the default spiller.

Splitting intervals as described above may improve the performance of generated
code in some circumstances. This work is experimental however, and it still
miscompiles many benchmarks. It's not recommended for general use yet.

llvm-svn: 90951

PerformObjectArgumentInitialization from BuildCXXMemberCallExpr.

llvm-svn: 90950

llvm-svn: 90949

In CXXRecordDecl::forallBases, add the base to the "queue", so we walk more than one heirarchy of classes. John, please review.

llvm-svn: 90948

llvm-svn: 90947

Fix crash in DisplayFunction().  ObjCInterfaceDecls can also get passed to this function, but we don't want to display them.

llvm-svn: 90944

llvm-svn: 90943

llvm-svn: 90940

using value decls;  we optimistically assume they won't turn into conflicts.
Teach it to tell the caller *why* the function doesn't overload with the returned
decl;  this will be useful for using hiding.

llvm-svn: 90939

Move the missing prototypes checking out into a new function. Don't warn about inline functions. Add a test.

llvm-svn: 90938

llvm-svn: 90937

type of the builtin when generating the function declaration for a builtin
library call.

llvm-svn: 90936

Pass the current SourceLocation to getAssignOperatorMethod, fixing a crash when the assign operator method needs to be instantiated. Doug, please review the updated default-assignment-operator.cpp change.

llvm-svn: 90935

llvm-svn: 90934

by the test case in PR 5627.  Essentially we shouldn't clear the
ExplodedNodeSet where we deposit newly constructed nodes if that set
is the 'Dst' set passed in.  It is not okay to clear that set because
it may already contain nodes.

llvm-svn: 90931

stores is not phi translating, thus it miscompiles really
crazy testcases.  This is from inspection, I haven't seen
this in the wild.

llvm-svn: 90930

llvm-svn: 90929

llvm-svn: 90927

phi translation of complex expressions like &A[i+1].  This has the
following benefits:

1. The phi translation logic is all contained in its own class with
   a strong interface and verification that it is self consistent.

2. The logic is more correct than before.  Previously, if intermediate
   expressions got PHI translated, we'd miss the update and scan for
   the wrong pointers in predecessor blocks.  @phi_trans2 is a testcase
   for this.

3. We have a lot less code in memdep.

We can handle phi translation across blocks of things like @phi_trans3,
which is pretty insane :).

This patch should fix the miscompiles of 255.vortex, and I tested it 
with a bootstrap of llvm-gcc, llvm-test and dejagnu of course.

llvm-svn: 90926

llvm-svn: 90925

all of g++'s bugs.

llvm-svn: 90924

Remove tests that are not suitable anymore. Plus they are not testing the original bugfixes anymore. These tests were inserted to check bug fixes in code that handled debug info intrinsics. These intrinsics are no longer used and now llvm parser simply ignores old .dbg intrinsics from these dead tests. 

llvm-svn: 90923

Move isConsecutiveLoad to SelectionDAG. It's not target dependent and it's primary used by selectdag passes.

llvm-svn: 90922

llvm-svn: 90920

llvm-svn: 90919

llvm-svn: 90918

llvm-svn: 90917

llvm-svn: 90915

pointers thereof) to their corresponding non-noreturn function
types. This conversion is considered an exact match for
overload-resolution purposes. Note that we are a little more strict
that GCC is, because we encode noreturn in the type system, but that's
a Good Thing (TM) because it does not allow us to pretend that
potentially-returning function pointers are non-returning function
pointers.

Fxies PR5620.

llvm-svn: 90913

Somehow opt was missed when this was added.

llvm-svn: 90912

that Chris noticed.

llvm-svn: 90910

the translated value back to it if an instruction.

llvm-svn: 90909

llvm-svn: 90908

match $ correctly with \r\n, unfortunately.

llvm-svn: 90907

llvm-svn: 90906

examines; fall back to a conservative answer if there are
more. This works around some several compile time problems
resulting from BasicAliasAnalysis calling PointerMayBeCaptured.

The value has been chosen arbitrarily.

This fixes rdar://7438917 and may partially address PR5708.

llvm-svn: 90905

llvm-svn: 90902

date when instsimplify kicks in.

llvm-svn: 90901

llvm-svn: 90898

llvm-svn: 90897