it's only really useful if you're going to crash anyways. Use it in the pretty stack trace
printer to kill the compiler if we hang while printing the stack trace.

llvm-svn: 177962

Sooooo many of these had incorrect or strange main module includes.
I have manually inspected all of these, and fixed the main module
include to be the nearest plausible thing I could find. If you own or
care about any of these source files, I encourage you to take some time
and check that these edits were sensible. I can't have broken anything
(I strictly added headers, and reordered them, never removed), but they
may not be the headers you'd really like to identify as containing the
API being implemented.

Many forward declarations and missing includes were added to a header
files to allow them to parse cleanly when included first. The main
module rule does in fact have its merits. =]

llvm-svn: 169131

llvm-svn: 141163

Luis Felipe Strano Moraes!

llvm-svn: 129558

new gcc warning that complains on self-assignments and
self-initializations.

llvm-svn: 122458

Try to fix building on the wayback machine.

llvm-svn: 120801

llvm-svn: 120298

llvm-svn: 110527

llvm-svn: 107042

Remove library check and regenerate configure.

llvm-svn: 107028

llvm-svn: 106576

llvm-svn: 104300

SmallString::c_str.

llvm-svn: 79456

Varga!

llvm-svn: 75897

llvm-svn: 74227

explicitly flush it.

llvm-svn: 67526

llvm-svn: 66279

llvm-svn: 66264

feels a kinship to machine stacks that grow down.  Now we get
stuff like this:

Stack dump:
0.	Program arguments: clang clang_crash_Iw2Osj.mi 
1.	/Developer/SDKs/MacOSX10.5.sdk/usr/lib/gcc/i686-apple-darwin9/4.0.1/include/xmmintrin.h:624:1: parsing function body '_mm_cvtpi16_ps'
2.	/Developer/SDKs/MacOSX10.5.sdk/usr/lib/gcc/i686-apple-darwin9/4.0.1/include/xmmintrin.h:624:1: in compound statement ('{}')
Abort

llvm-svn: 66145

llvm-svn: 66144

that get printed when a program crashes.  This is the first step of many.

llvm-svn: 66076