Signed-off-by: Vinzenz Feenstra <evilissimo@gmail.com>

Signed-off-by: Vinzenz Feenstra <evilissimo@gmail.com>

- Added dir0 which would in theory return the local scope, but
  for just returns the content of the builtins module
- Added a unit test file for dir which won't print anything as the
  list sorting does not work as expected at the moment
  (missing full implementation) and the attributes are different
  as well (pyston has some CPython 2.7.5 does not have and vice versa)
- dir1 implements the lookup on a passed object
  - If the object has a __dir__ method, it will call it and return the result
    returned by this method
  - Otherwise all class and instance attributes and methods are returned
  - If the object has a __dict__ attribute, additional to the previous one
    it will return the keys from that one as well
Signed-off-by: Vinzenz Feenstra <evilissimo@gmail.com>

Signed-off-by: Vinzenz Feenstra <evilissimo@gmail.com>

Signed-off-by: Vinzenz Feenstra <evilissimo@gmail.com>

For the release build, was building both tools/ and tools/llc (and tools/opt),
which could potentially run at the same time and interfere with each other.

These seem to work fairly well as tests since
- they don't use any external libraries, and
- they have a very straightforward input-to-output model

Added some more runtime functions
gcj_2014_2d is currently crashing pyston

The presence of an allocated "elts" pointer is determined by capacity>0,
but the GC handler was incorrectly only choosing to visit it if size>0.
Not all code paths free the elts array if size goes down to zero, so
it could happen that capacity>0 and size=0, and then the elts array would
not be tracked even though it was expected to be.

Added a test that illustrates this.

Implement str.lstrip and str.rstrip

Added hasattr implementation buildin

Implement dict iterators

Removed assert from str to make __iter__ work again

fix lint.py

Compiling fixes

Unlike some other languages, it looks like eval()
doesn't force the capturing of outer variables.

Good thing too, since pretty much any function call
could theoretically end up resolving to eval().

I think the new version of LLVM changed clang-format, and
it reformatted parts of the Pyston codebase.
Maybe we should pin the rev for clang-format?

If you throw an unhandled exception, you'll see a traceback
from the top-level handler.  Doesn't enable us to run any additional
programs, since this functionality isn't available to Python-level code,
but hopefully should make debugging easier.

Python inheritance is remarkably complicated... this commit implements the basics.
There are still a fair number of things that are unimplemented, and some things
like inheriting from all the basic types haven't been added yet.

Similar to the location of the dict attribute in CPython,
the 'hc attrs list' in Pyston will end up being located at
different offsets, depending on the class that's being subclassed
from.

This commit removes the HCBox class, which assumes that it always lives
at the same offset and so can be statically described with a C++ class,
and instead uses a runtime lookup.

This should hopefully make things a fair bit closer to supporting inheritance.

Add (modified) spectral_norm millibenchmark from the language shootout.

Implement tuple hashing