- Removed old, deprecated TODO on libunwind section.
- Added zsh dependency
- Fixed subtle typo in LLVM + clang section
- Replaced hardcoded source filename in the error messages by __FILE__.
- Fixed subtle bug in getReverseOpName(): the reverse of AST_TYPE::NotEq and the reverse of AST_TYPE::Eq were wrong (ironically, they were reversed!)
Fixing the subtle "bug" apparently makes pyston fail some tests, so I'm backing out on this. It doesn't make much sense that the reverse of NotEq is NotEq, and the reverse of Eq is Eq... this needs to be rechecked by someone that knows the code better than me.
Removed deprecated TODO from ast.cpp. getReverseOpName() is totally fine.
Add int ** float, and now the polymorphism test is closer to working
Source control fail: I started pyston from the wrong icbd branch.

Merge in the changesets that were missed:
- type recording
- better polymorphic IC performance
- build system improvements
- update to what was llvm trunk
clean up whitespace
Allow the re-usage of AST nodes for now, though it's muddies some things
Improve the error messages here
Add the ability to link against a debug build of libunwind for debugging unwinding issues, and some basic instructions on how to do so
Pending libunwind patch
Notes
Merge pull request #31 from filipegoncalves/master

Removing hardcoded filename in ast.cpp
Update optimization passes to use the latest LLVM changes

LLVM had some breaking changes that I didn't notice; on the plus
side this new range-iteration style is much nicer.
rangify the codebase
Add an extra marker to libunwind so that pyston can ensure it's running on a patched libunwind version
Improve valgrind hooking, though I'm not sure if it's helpful yet
Switch all graph work to be based on Blocks, not their indices

This means we can have non-consecutive block indices, which
is a prereq for things like merging blocks.
Not sure how worth it this was
Make pyc generation slightly more robust by adding a length

I think I generated an invalid pyc file by ctrl-C'ing while it was
writing out a file, and it took me a while to figure out why the
parser kept crashing.
Ideally this should be a full checksum.
Turn on some more warnings, though the ones that don't have many false positives aren't very helpful