That could be it. If that is the case how would I take apart the argument from the opcode?
>> On Oct 27, 2021, at 2:41 PM, Timothy Baldridge <tbaldri...@gmail.com> wrote: >> >> Aren't all opcodes a single byte in length? Are you maybe combining >> the opcode argument with the opcode? >> >> On Wed, Oct 27, 2021 at 12:09 PM M A <teammember0...@gmail.com> wrote: >>> >>> Hi, would anyone know what instruction/opcode 320 does? I'm in the file >>> pyopcode.py tracing a problem to dispatch_bytecode(). The problem I have >>> encountered happens when next_instr and self.last_instr are both equal to >>> 320. I have tried looking at the file opcode.py. There was no mention of >>> 320 anywhere. Any hints or help would be great. >>> >>> Thank you. >>> _______________________________________________ >>> pypy-dev mailing list >>> pypy-dev@python.org >>> https://mail.python.org/mailman/listinfo/pypy-dev >> >> >> >> -- >> “One of the main causes of the fall of the Roman Empire was >> that–lacking zero–they had no way to indicate successful termination >> of their C programs.” >> (Robert Firth) > _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
