Stefan Behnel, 12.03.2012 10:21: > Amaury Forgeot d'Arc, 12.03.2012 09:37: >> 2012/3/12 Stefan Behnel: >>>> It's tersely documented in pypy/doc/coding_guide.rst. >>> >>> I read this a little closer now and it told me more or less what I expected >>> when I skipped over it for the first time. It tells me that "PyPy can be >>> debugged on top of CPython", which is (in friendly words) only true if you >>> are prepared to fire it up before going to bed to get the results the next >>> morning. I thought we had to 60's for that. >> >> Did we tell you that cpyext was slow? :-) > > Oh, believe me, I'd be happy if everything was running in C and only using > cpyext.
Rethinking this some more - I'd be *really* happy if everything was just C. Armin noted that the RPython-to-C translation is basically a 1:1 mapping (plus type specialisation). So, if the generated C code is any usable and if the nightly builds had debugging symbols in them, I could just run gdb and callgrind over them and they would pinpoint the obvious problems immediately. Would that work? And if so, could someone enable that? Stefan _______________________________________________ pypy-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-dev
