rocky 1fc8ac4700 Interval order COME_FROMs in Python3 ...

This bug had possibly caused lots of grammar pollution which may need
addressing.

We want to process COME_FROMs to the same offset to be in *descending*
order so we have the larger range or biggest instruction interval
last. (I think they are sorted in increasing order, but for safety
we sort them). That way, specific COME_FROM tags will match up
properly. For example, a "loop" with an "if" nested in it should have
the "loop" tag last so the grammar rule matches that properly

Adjust Python 3 grammar for more COME_FROM -> COME_FROM_LOOP. And
remove optional COME_FROM_LOOP where possible. Previously, the
optional-ness was a result of inner nestings gobbling up the
COME_FROM.

We'll probably want to go back and fix this up in Python2.

2016-09-26 09:26:51 -04:00

..

bin

resolve merge conflicts from pull request

2016-08-10 08:20:51 +02:00

parsers

Interval order COME_FROMs in Python3

2016-09-26 09:26:51 -04:00

scanners

Interval order COME_FROMs in Python3

2016-09-26 09:26:51 -04:00

semantics

fixed generation of FSTRING_CONVERSION_MAP in < python 2.7

2016-09-21 22:13:25 +02:00

__init__.py

Use xdis for code, magics, and marshal

2016-05-27 19:18:06 -04:00

disas.py

disassemble -> ingest where appropriate

2016-09-04 11:43:02 -04:00

main.py

disassemble -> ingest where appropriate

2016-09-04 11:43:02 -04:00

Makefile

Lint stuff

2015-12-11 18:49:23 -05:00

parser.py

Interval order COME_FROMs in Python3

2016-09-26 09:26:51 -04:00

scanner.py

disassemble -> ingest where appropriate

2016-09-04 11:43:02 -04:00

show.py

disassemble -> ingest where appropriate

2016-09-04 11:43:02 -04:00

verify.py

Try stronger verification

2016-09-25 17:48:33 -04:00

version.py

Get ready for release 2.8.3

2016-09-11 19:22:07 -04:00