the end of it is dead.", which appears to break bootstrapping LLVM.

llvm-svn: 143668

llvm-svn: 143667

llvm-svn: 143666

llvm-svn: 143664

have the correct value in the IRInterpreter.

llvm-svn: 143663

 - Basically, we coordinate with llvm-build to create a Makefile fragment we can
   easily use. For now, nothing is wired in except the support to automatically
   regenerate this file when necessary.

llvm-svn: 143662

llvm-svn: 143661

across calls, and only check for nested dependences on the special
call-sequence-resource register.

llvm-svn: 143660

llvm-svn: 143659

llvm-svn: 143658

the second pass reports warnings/errors.  This has the effect that we follow 
the more canonical "last option wins" paradigm when there are conflicting 
options.
rdar://10383776

Previously, we parsed the warning options in order.  This caused non-intuitive
behavior:

1) clang test.c -Wnosuchwarning -Wno-unknown-warning-option
Before:
warning: unknown warning option '-Wnosuchwarning' [-Wunknown-warning-option]
1 warning generated.
After:
[0 warning generated.]

2) clang test.c -Wnosuchwarning -Werror=unknown-warning-option
Before:
warning: unknown warning option '-Wnosuchwarning' [-Wunknown-warning-option]
1 warning generated.
After:
error: unknown warning option '-Wnosuchwarning' [-Werror,-Wunknown-warning-option]

3) clang test.c -Werror=unknown-warning-option -Wnosuchwarning -Wno-error=unknown-warning-option -Wnosuchwarning
Before:
error: unknown warning option '-Wnosuchwarning' [-Werror,-Wunknown-warning-option]
warning: unknown warning option '-Wnosuchwarning' [-Wunknown-warning-option]
After:
warning: unknown warning option '-Wnosuchwarning' [-Wunknown-warning-option]
warning: unknown warning option '-Wnosuchwarning' [-Wunknown-warning-option]
2 warnings generated.

4) clang test.c -Werror=unknown-warning-option -Wnosuchwarning -Wno-error=unknown-warning-option -Wno-unknown-warning-option -Wnosuchwarning
Before:
error: unknown warning option '-Wnosuchwarning' [-Werror,-Wunknown-warning-option]

After:
[0 warning generated.]

llvm-svn: 143657

on internal only (public API hasn't changed) to simplify the paramter list
to the launch calls down into just one argument. Also all of the argument,
envronment and stdio things are now handled in a much more centralized fashion.

llvm-svn: 143656

utils: Remove (way) old nightly test scripts, I don't think anyone uses them and LNT has way better tools than this.

llvm-svn: 143655

We currently run the old memory access checker in parallel, as we would
otherwise fail in TempScop because of currently unsupported functions. We will
remove the old memory access checker as soon as TempScop is fixed.

llvm-svn: 143654

llvm-svn: 143653

llvm-svn: 143652

llvm-svn: 143651

llvm-svn: 143650

know at build time.

llvm-svn: 143649

component needs to include files from its ObjDir.

llvm-svn: 143648

llvm-svn: 143647

llvm-svn: 143646

Fix the alignment on scalar parameter variables so that it matches what the AST thinks it should be.  Per report on cfe-dev.

llvm-svn: 143645

A PCH file keeps track of #pragma diagnostics state; when loading the preamble, they conflicted
with the #pragma diagnostic state already present in the DiagnosticsEngine object due to
parsing the preamble.

Fix this by clearing the state of the DiagnosticsEngine object.
Fixes rdar://10363572 && http://llvm.org/PR11254.

llvm-svn: 143644

llvm-svn: 143643

llvm-svn: 143642

 - llvm-build should now be Python2.4 compatible as best I know.

llvm-svn: 143641

llvm-svn: 143640

llvm-svn: 143639

llvm-svn: 143638

llvm-svn: 143637

contains fields.

llvm-svn: 143636

accessibility. Fixes <rdar://problem/3727335>.

llvm-svn: 143635

llvm-svn: 143634

llvm-svn: 143633

llvm-svn: 143631

Only currently done if the later store is writing to a power of 2 address or 
has the same alignment as the earlier store as then its likely to not break up
large stores into smaller ones

Fixes <rdar://problem/10140300>

llvm-svn: 143630

header.

llvm-svn: 143629

dependency table used by llvm-config.

llvm-svn: 143628

llvm-svn: 143627