fixes #169 - allow a negative step in xrange
Rebase LLVM rev
Merge remote-tracking branch 'upstream/master'
adds test cases for xrange with a negative step and xrange(0)
Merge pull request #176 from dagar/master

fixes #169 - allow a negative step in xrange
Stopgap for rewrite-being-too-large

Just let the rewrite continue but stop emitting any assembly,
and then at the end abort the rewrite.
Fix isAllocCall check
Add my pending-review patch for invoking patchpoints

Will get rid of it once it's merged upstream
Forgot to include this part
docs: minor fix on installing instructions
Merge branch 'mjisyang-develop'

Closes PR #188
For now, disallow allocation of callee-save registers in inline caches

If we allocate a callee-save register that the parent function had
not also allocated, change its value, and then call a function
that then unwinds, the unwinder would pass the new (incorrect)
value of the callee save register to the next frame.

We either need to
- make sure callee-save registers are restored before any potentially-throwing
  callsite, or
- make the unwinder able to restore these registers for us, potentially
  by writing our own exception unwinder.

For now, the easiest thing to do is to disallow allocation of those registers.
(I'm not even sure how much we allocate them at all at the moment.)
Merge pull request #183 from undingen/isAlloc

Fix isAllocCall check
Enable patching of invokes

With the LLVM patch, it seems like this works.
Fix embedding of constant ints

Allow 64-bit constants.  not sure how we didn't run into this before
Separate the CompilerType objects from the class definitions

Most code wants to have access to the basic types (INT, STR, etc)
but doesn't need to know anything about what methods they support.

Move the commonly-accessed parts of compvars.h into the always-included
core/types.h, and remove almost all of the includes of compvars.h
Add some extra error checking during irgen
Add some more patchpoint-related llvm patches
Add the ability to represent bools as non-i1

Turned off for now; will need this for a later patch.
Change how we create and represent patchpoints