- 04 Sep, 2015 23 commits
-
-
Rudi Chen authored
-
Rudi Chen authored
This will reallocate all objects in the small heap and update all references that were pointing to this object. This is not functional yet, there are still references that we are not tracking at other points in the program, so it's still gated behind the MOVING_GC flag.
-
Rudi Chen authored
- Refactor the stack logic into a separate data structure ChunkedStack, keep the push function that deals with marking as functionality specific to a subclass of ChunkedStack (no virtual, just reuse code). - Add an additional (disabled) phase that maps out the reference graph reachable objects after the sweep phase. Prepare moving all objects in the small heap. Also, rename TraceStack to TraversalWorklist because the fact that we're using a stack is an implementation detail.
-
Rudi Chen authored
Moving gcs will need this to update pointers. There should not be any extra dereference, it will just happen on the other side of the function. Use templates to avoid direct (void**) casts -- make sure we're always passing an pointer of the form T**.
-
Rudi Chen authored
-
Rudi Chen authored
It's easier to tell the two constants apart if they are different.
-
Rudi Chen authored
They tends to time out or just make the test suite run for longer. They definitely times out when running a prototype moving gc.
-
Kevin Modzelewski authored
Scan constants written into compiled code.
-
Rudi Chen authored
A GC could happen during the rewrite.
-
Rudi Chen authored
-
Rudi Chen authored
-
Kevin Modzelewski authored
Scan rewriters for interior pointers
-
Rudi Chen authored
We need to do this because the ICInvalidator pointers are stored inside Pyston heap objects.
-
Kevin Modzelewski authored
Some improvments that let test_index could pass
-
Kevin Modzelewski authored
Sqlalchemy compatibility fixes
-
Kevin Modzelewski authored
-
Kevin Modzelewski authored
-
Kevin Modzelewski authored
Sqlalchemy subclasses set, and overrides __init__ and does some custom initialization there. We were doing the initialization in __new__, which works most of the time, except if a generator was passed since then sqlalchemy's initialization will see what looks like an empty generator since we already consumed it. So move the initialization to init. Except for frozenset which still needs to do it in new.
-
Kevin Modzelewski authored
In CPython, str.add directly throws a TypeError since it is implemented as a sq_concat. sqlalchemy relies on being able to do str()+MyStr() and use MyStr.__radd__ to handle the addition. We were throwing a TypeError but not implementing it in sq_concat. So instead, return NotImplemented instead of directly throwing a TypeError. This makes '+' more compatible but str.__add__ a bit less compatible.
-
Boxiang Sun authored
add _PyLong_Copy implementation, return a copy in PyNumber_Long if the type of argument is long or long subclass
-
Boxiang Sun authored
-
Boxiang Sun authored
-
Boxiang Sun authored
-
- 03 Sep, 2015 2 commits
-
-
Kevin Modzelewski authored
Add override keyword where necessary.
-
Rudi Chen authored
-
- 02 Sep, 2015 10 commits
-
-
Rudi Chen authored
-
Kevin Modzelewski authored
Generate better module names to make the object cache more effective
-
Kevin Modzelewski authored
add tp_nextiter implementation for our iterators
-
Marius Wachtler authored
-
Marius Wachtler authored
-
Marius Wachtler authored
one of the problems were that depending on if all files were all ready parsed we JITed more or less functions, this changed the total number of jited functions which changed all the module names. This lead to the result that in order to have all entries inside the cache we needed at least 3runs if the pyc files were old. The whole name scheme should add some point get improved but for now it should be enough.
-
Kevin Modzelewski authored
Lower initial dict/set size from 64->8
-
Kevin Modzelewski authored
Support non-module-globals in the llvm tier
-
Kevin Modzelewski authored
-
Kevin Modzelewski authored
-
- 01 Sep, 2015 5 commits
-
-
Kevin Modzelewski authored
By switching to our DenseMap/Set fork with that allows parameterizing on this. This is the same number that CPython uses. We were previously using llvm's default of 64, which is pretty high -- probably fine for their use cases, but in Python programs with lots of sets/dicts we spend a lot of time doing malloc() for all those 1kB+ allocations. This also increases the time it takes to iterate over the dict/set, since there are more empty buckets that have to be read + skipped.
-
Kevin Modzelewski authored
The default is 64, which is quite a lot for our uses.
-
Kevin Modzelewski authored
-
Kevin Modzelewski authored
- add note + license - put in our namespace - change header guards - make it match our lint style - don't apply our formatting
-
Kevin Modzelewski authored
With no modificaions in this commit, so that we can track changes. Unmodified from llvm rev r230300.
-