OpcodeFor in ir.cc scans a static array (opcodetab) looking for a sentinel that
isn't there. The upshot is memory corruption in --nonative mode.
I have no specific test for this, but the memory corruption problems suddenly
went away when I noticed and fixed this bug.
The patched code respects a proper array bound on the loop control variable.
Original issue reported on code.google.com by aecolley on 13 Oct 2013 at 9:09
Original issue reported on code.google.com by
aecolleyon 13 Oct 2013 at 9:09Attachments: