testsuite regression with a coming patch.

llvm-svn: 77832

ENABLE_EXPENSIVE_CHECKS clean on x86_64-.*-darwin10.

llvm-svn: 77831

llvm-svn: 77830

llvm-svn: 77829

llvm-svn: 77828

llvm-svn: 77827

llvm-svn: 77826

llvm-svn: 77824

project under the normal license, yay. :)

llvm-svn: 77823

llvm-svn: 77821

llvm-svn: 77820

to:

.quad X

even on a 32-bit system, where X is not 64-bits.  There isn't much that
we can do here, so we just print:

.quad	((X) & 4294967295)

instead.

llvm-svn: 77818

llvm-svn: 77817

the appropriate subclasses.

llvm-svn: 77815

llvm-svn: 77814

llvm-svn: 77813

llvm-svn: 77812

llvm-svn: 77811

llvm-svn: 77810

llvm-svn: 77808

llvm-svn: 77807

llvm-svn: 77806

llvm-svn: 77805

llvm-svn: 77804

should have no state that is specific to particular globals in the
section.  In this case, it means the removal of the "isWeak" and
"ExplicitSection" bits.  MCSection uses the new form of SectionKind.

To handle isWeak, I introduced a new SectionInfo class, which is
SectionKind + isWeak, and it is used by the part of the code generator
that does classification of a specific global.

The ExplicitSection disappears.  It is moved onto MCSection as a new
"IsDirective" bit.  Since the Name of a section is either a section
or directive, it makes sense to keep this bit in MCSection.  Ultimately
the creator of MCSection should canonicalize (e.g.) .text to whatever
the actual section is.

llvm-svn: 77803

serious issues :)

llvm-svn: 77800

llvm-svn: 77796

llvm-svn: 77795

actually characters.

llvm-svn: 77794

llvm-svn: 77793

llvm-svn: 77792

llvm-svn: 77791

llvm-svn: 77790

llvm-svn: 77789

llvm-svn: 77788

llvm-svn: 77787

llvm-svn: 77786

myself because I'm getting tired of seeing the red buildbots, which have 
been red since 5:30PM PDT last night.

Proposed supplement to developer policy: committers should make sure to 
be around to watch for buildbot failures after committing.

llvm-svn: 77785

 - Off by default, you can test it with the --no-sh argument.

 - For me it works for all but 3 tests, but there a number of FIXMEs and QOI
   issues:  
     o Redirection isn't completely accurate -- in practice it can't portably
       be, but I would like to error out if someone writes something which isn't
       going to work. This is the source of the 3 test failures.

     o Some pipe configurations have the potential to deadlock.

     o It is significantly slower when multithreaded. I believe this is due to
       locking happening under the hood, there is probably some kind of solution
       but I haven't investigated yet.

     o Log output is ugly.

llvm-svn: 77784

 - Empty arguments weren't handled correctly.
 - Escapes outside quoted strings weren't handled.

llvm-svn: 77783