do you mind if I ask a more general pyston question? I am a little confused by the aim of the project to be honest
is it a) to be faster than pypy for the type of code dropbox cares about (but maybe not for lots of other code that dropbox doesn't care about) and/or b) to be faster than cpython on a range of python code that pypy can't easily support?
because being faster than pypy in general seems very hard
and I'm surprised that pypy is unable to speed up your script because I think that's something were pypy should do well but like the said the properly just don't handle a particular path in there tracer which is very important for this benchmark and if they would add it (no idea how complicated) I would expect it to get much faster that it is now.
@kmod I too thought about having a fixed offset for the vregs from the base pointer but than I was not sure how I can implement it. It should be possbile with a custom pass which adjust the frame layout llvm emits but that does not sound like a too good approach. Do you have an idea for a easier way?
and I will tomorrow investigate the llvm generated asm code in order to better understand what llvm does and what is slowing down things or speeding up stuff for the frame handling stuff