llvm-svn: 63689

llvm-svn: 63687

from SelectionDagBuild.

llvm-svn: 63680

llvm-svn: 63677

llvm-svn: 63676

llvm-svn: 63675

llvm-svn: 63674

have it yet.  More coming.

llvm-svn: 63673

Do not let dbg intrinsic block folding of two entry phi node.

llvm-svn: 63671

If "optimize for size" attribute is set then block non-trivial loop unswitches but allow trivial loop unswitches.

llvm-svn: 63670

llvm-svn: 63664

llvm-svn: 63663

llvm-svn: 63660

llvm-svn: 63659

renaming it to ConvertScalar_ExtractValue

llvm-svn: 63658

llvm-svn: 63656

llvm-svn: 63653

no functionality change.

llvm-svn: 63652

functionality change.

llvm-svn: 63651

llvm-svn: 63650

aggregate values.  loads are not yet handled (coming
soon to an sroa near you).

llvm-svn: 63649

basic-block segments bottom-up instead of top down. This
is the first step in a general restructuring of the way
register liveness is tracked in the post-RA scheduler.

llvm-svn: 63643

is given, override the subtarget settings and enable 64-bit support.
This restores the earlier behavior, and fixes regressions on
Non-64-bit-capable x86-32 hosts.

This isn't necessarily the best approach, but the most obvious
alternative is to require -mcpu=x86-64 or -mattr=+64bit to be used
with -march=x86-64 when the host doesn't have 64-bit support. This
makes things little more consistent, but it's less convenient, and
it has the practical drawback of requiring lots of test changes, so
I opted for the above approach for now.

llvm-svn: 63642

Duncan spotted this. Thanks!

llvm-svn: 63641

accessed at least once as a vector.  This prevents it from
compiling the example in not-a-vector into:

define double @test(double %A, double %B) {
	%tmp4 = insertelement <7 x double> undef, double %A, i32 0
	%tmp = insertelement <7 x double> %tmp4, double %B, i32 4
	%tmp2 = extractelement <7 x double> %tmp, i32 4
	ret double %tmp2
}

instead, producing the integer code.  Producing vectors when they
aren't otherwise in the program is dangerous because a lot of other
code treats them carefully and doesn't want to break them down.
OTOH, many things want to break down tasty i448's.

llvm-svn: 63638

and that sroa doesn't crash.

llvm-svn: 63637

in any old order.  Since analyzing a node analyzes its
operands also, this can mean that when we pop a node
off the list of nodes to be analyzed, it may already
have been analyzed.

llvm-svn: 63632

llvm-svn: 63631

with a specified alignment.

llvm-svn: 63629

llvm-svn: 63623

llvm-svn: 63622

needed to build the LLVM gold plugin.

llvm-svn: 63621

llvm-svn: 63620

llvm-svn: 63618

llvm-svn: 63616

llvm-svn: 63600

llvm-svn: 63599

initial PHI nodes of the machine function.

llvm-svn: 63598

the index of the value being extracted is always an i32.  This fixes PR3465

llvm-svn: 63597

crazy cases like:

struct f {  int A, B, C, D, E, F; };
short test4() {
  struct f A;
  A.A = 1;
  memset(&A.B, 2, 12);
  return A.C;
}

llvm-svn: 63596