llvm-svn: 90040

inserted instructions.  No functionality change until someone starts using it.

llvm-svn: 90039

way that getUnderlyingObject does it. 

This fixes the 'DecomposeGEPExpression and getUnderlyingObject disagree!' 
assertion on sqlite3.

llvm-svn: 90038

if we don't have an address expression available in a predecessor,
then model this as the value being clobbered at the end of the pred
block instead of being modeled as a complete phi translation failure.
This is important for PRE of loads because we want to see that the
load is available in all but this predecessor, and complete phi
translation failure results in not getting any information about
predecessors.

This doesn't do anything until I renable code insertion since PRE
now sees that it is available in all but one predecessors, but can't
insert the addressing in the predecessor that is missing it to 
eliminate the redundancy.

llvm-svn: 90037

btw, I believe that isMicrosoftInteger can go away; it's not read anywhere

llvm-svn: 90036

llvm-svn: 90035

llvm-svn: 90034

llvm-svn: 90033

llvm-svn: 90032

llvm-svn: 90031

llvm-svn: 90030

Move program actions implications to clang::InitializeFrontendOptions which already contains such logic.

llvm-svn: 90029

llvm-svn: 90028

DeclarationName can't handle them yet, so right now Parser just errors out on them.

llvm-svn: 90027

llvm-svn: 90026

GetCXXBaseClassOffset to actually pass the test.

llvm-svn: 90025

We always want to create a virtual function pointer entry if the path from the derived return value to the base overridden return value contains a virtual base class.

llvm-svn: 90024

llvm-svn: 90023

to inform GVN about the newly inserted values.  This fixes 
PR5631.

llvm-svn: 90022

llvm-svn: 90021

llvm-svn: 90020

fixes PR5630 and sets the stage for the next phase of goodness (testcase
pending).

llvm-svn: 90019

Add a new PrimaryBaseInfo struct that combines the record decl of a primary base with whether it's virtual or not.

llvm-svn: 90018

llvm-svn: 90017

llvm-svn: 90016

for pointing this out.

llvm-svn: 90015

llvm-svn: 90014

translation of add with immediate.  This allows us
to optimize this function:

void test(int N, double* G) {
  long j;
  G[1] = 1;
    for (j = 1; j < N - 1; j++)
        G[j+1] = G[j] + G[j+1];
}

to only do one load every iteration of the loop.

llvm-svn: 90013

add two simple test cases we now optimize (to one load in the loop each) and one we don't (corresponding to the fixme I added yesterday).

llvm-svn: 90012

llvm-svn: 90011

llvm-svn: 90009

the FIXME I added yesterday to be implemented.

llvm-svn: 90008

array indexes.  The "complex" case of SRoA still handles them, and correctly.

This fixes a weirdness where we'd correctly avoid transforming A[0][42] if
the 42 was too large, but we'd only do it if it was one gep, not two separate
ones.

llvm-svn: 90007

llvm-svn: 90006

the problem only shows for msp430 and pic16 which is why it specifies
them using -march.  But it is wrong to put such tests in CodeGen/Generic,
since not everyone builds these targets.  Put a copy of the test in each
of the target test directories.

llvm-svn: 90005

llvm-svn: 90004

llvm-svn: 90003

llvm-svn: 90002

llvm-svn: 90001

fixes a crash analyzing consumer-lame, which had an "%X = add %X, 1"
in unreachable code.

llvm-svn: 90000