llvm-svn: 26209

llvm-svn: 26208

llvm-svn: 26207

llvm-svn: 26206

like the flex stuff, which actually works when people do cvs updates and
get conflicts in the updated checked in file.

llvm-svn: 26205

it, because this:

.bss
X:
.byte 0

results in the assembler warning: "initialization in bss segment".  Annoying.

llvm-svn: 26204

llvm-svn: 26203

The ABI specifies that there is a register save area at the bottom of the
stack, which means the actual used pointer needs to be an offset from
the subtracted value.

llvm-svn: 26202

GCC's syntax for auto-dependency generation stuff. This should
be changed to be disabling dependency stuff unless GCC/ICC is
found.

llvm-svn: 26201

llvm-svn: 26200

llvm-svn: 26199

go through, but we do want to know if we're using GCC/ICC since they
share certain funky command line options (for dependency generation
stuff)

llvm-svn: 26198

llvm-svn: 26197

llvm-svn: 26196

ops.

llvm-svn: 26195

llvm-svn: 26194

llvm-svn: 26193

llvm-svn: 26192

llvm-svn: 26191

llvm-svn: 26190

can provide work for the outer loop to canonicalize.

This fixes a case that breaks unswitching.

llvm-svn: 26189

llvm-svn: 26188

block in the appropriate loop nest.

Third time is the charm, right?

llvm-svn: 26187

llvm-svn: 26186

emit it (instead of .space), saving a bit of space in the .o file.

For example:
int foo[100];
int bar[100] = {};

when compiled with C++ or -fno-common results in shrinkage from 1160 to 360
bytes of space.  The X86 backend can also do this on darwin.

llvm-svn: 26185

llvm-svn: 26184

llvm-svn: 26183

XMM registers were not being handled.

llvm-svn: 26182

llvm-svn: 26181

llvm-svn: 26180

llvm-svn: 26179

llvm-svn: 26178

llvm-svn: 26177

llvm-svn: 26176

llvm-svn: 26175

llvm-svn: 26174

llvm-svn: 26173

maxStoresPerMemMove. Although the last one is not used.

llvm-svn: 26172

target specific theshold, e.g. 16 for x86.

llvm-svn: 26171

llvm-svn: 26169