LLVM 3.2 Support

LLVM 3.2 is out as of mid December. We need to update the backend to support it.

There seems to be a number of new bugs due to the change.

With LLVM 3.1 we get the following testsuite failures:

OVERALL SUMMARY for test run started at Mon Jan 14 21:42:32 PST 2013
    3552 total tests, which gave rise to
   13164 test cases, of which
       0 caused framework failures
   11606 were skipped

    1515 expected passes
      23 had missing libraries
      15 expected failures
       0 unexpected passes
       5 unexpected failures

Unexpected failures:
*  codeGen/should_run        cgrun044 [exit code non-0] (optllvm)
*  concurrent/should_run     367_letnoescape [bad exit code] (optllvm)
*  numeric/should_run        arith005 [bad stdout] (optllvm)
   typecheck/should_compile  tc226 [exit code non-0] (optllvm)
   typecheck/should_compile  tc235 [exit code non-0] (optllvm)

Where the failures marked with '*' are unique to the LLVM backend.

With LLVM 3.2 we get the following:

OVERALL SUMMARY for test run started at Tue Jan 15 16:02:01 PST 2013
    3552 total tests, which gave rise to
   13164 test cases, of which
       0 caused framework failures
   11606 were skipped

    1512 expected passes
      23 had missing libraries
      15 expected failures
       0 unexpected passes
       8 unexpected failures

Unexpected failures:
** codeGen/should_compile    1916 [exit code non-0] (optllvm)
** codeGen/should_run        cgrun028 [exit code non-0] (optllvm)
*  codeGen/should_run        cgrun044 [exit code non-0] (optllvm)
*  concurrent/should_run     367_letnoescape [bad exit code] (optllvm)
*  numeric/should_run        arith005 [bad stdout] (optllvm)
** numeric/should_run        numrun012 [exit code non-0] (optllvm)
   typecheck/should_compile  tc226 [exit code non-0] (optllvm)
   typecheck/should_compile  tc235 [exit code non-0] (optllvm)

Where failures marked with '*' are unique to the LLVM backend and failures marked with '**' are unique to LLVM 3.2 relative to 3.1.

I believe bootstrapping with LLVM also fails now. However, that may be due to the change to the new-code-generator, and not of LLVM 3.1 -> 3.2. I'll create a separate ticket for that.

NOTE: These test suite results were all generated on Mac OS X 10.8.