analysis_unittest
failed, any helps. The output seems a bit long. But I can put it here if you desired.
clfunc
related commit recently. Maybe one of these commit broke it?
pow(3l, 3l, -8)
, and already get some progress, most of the test_pow test could passed. But I don't know how to let longPow accept float parameter, pow(long, float, mod) will say TypeError: unsupported operand type(s) for ** or pow(): 'long' and 'float'
.
TypeError: pow() 3rd argument not allowed unless all arguments are integers
ZeroDivisionError: 0.0 cannot be raised to a negative power
in intPow.
min_max
, pow
, and long float
issues.
collections.defaultdict(arg)
. We rewrite this to but forget to add the call to defaultdict.tp_init
. This means on the first call it will succeed because during the rewrite we call it but the generated code does not contain the call...
typeCallInner()
types.cpp:922
// If we weren't passed the args array, it's not safe to index into it
if (passed <= 2)
initrtn = runtimeCallInternal(init_attr, NULL, init_argspec, arg2, arg3, NULL, NULL, keyword_names);
else
initrtn = runtimeCallInternal(init_attr, NULL, init_argspec, arg2, arg3, args[0], &args[1], keyword_names);
runtimeCallInternal
processDescriptor
doesn’t deal with rewriting right now
processDescriptor
, or if we just want to emit a call to processDescriptor
in the assembly
capsule
/* Wrap void * pointers to be passed between C modules */
:facepalm:
defaultdict
bug shows only up sometimes...
min()
specialized for taking ints)
a, b = b, a
a, b = l[0], l[1]
for i in range(10)
(the range) or True
, False
etc... do you plan to add type recording to getGlobal()? Because afaik we only supported getattr?
perf
usage
_int_malloc
and _int_free
anymore
PyErr_Occurred()
returns true, is there some easy way to dump the error to the console?
django_template.py 3.9s (2) 4.1s (2) +6.6%
not expected
0m3.742s
runtime. after doing rm build/Release/lib_pyston/grp.pyston.so
, runtime drops to 0m3.489s
BoxedClass
doesn’t seem to have all the functionality of BoxedHeapClass
BoxedHeapClass
es, I guess
BoxedHeapClass
es, we have the as_sequence
field and then point tp_as_sequence
at it, and if I turn, say, tuple_cls
into a BoxedClass
, then tp_as_sequence
won’t be pointed to anything and won’t be initialized right (I’m not really entirely sure how all that initialization works but it seems like it’s just wrapping the __iter__
method or something, is that right?)
BoxedHeapClass
, and that they actually seem to rely on its functionality of using attributes for this stuff just like Python classes do)