Skip to content

Ordering of itab.h and itab.c varies between runs and Python versions…#145

Open
martindorey wants to merge 1 commit intovmt:masterfrom
martindorey:master
Open

Ordering of itab.h and itab.c varies between runs and Python versions…#145
martindorey wants to merge 1 commit intovmt:masterfrom
martindorey:master

Conversation

@martindorey
Copy link
Copy Markdown

#144 (#144)

scripts/ud_opcode.py: Working on #120, because I hadn't realized that someone had already got properly to the root of it, in #139, I was hampered by the output, specifically itab.h, changing order every time I ran:

UD_OPCODE_DEBUG=1 python3 ../scripts/ud_itab.py ../docs/x86/optable.xml .

... from the libudis86/ directory. The getLabels change here fixes that to be in a defined ordering.

The mergeSSENONE change fixes the ordering differences I see in itab.c between running the above command and similar with python2, by iterating over each table in the same style as used by genOpcodeTable in class UdItabGenerator in scripts/ud_itab.py.

…mt#144 (vmt#144)

scripts/ud_opcode.py: Working on vmt#120, because I hadn't realized that someone had already got properly to the root of it, in vmt#139, I was hampered by the output, specifically itab.h, changing order every time I ran:

UD_OPCODE_DEBUG=1 python3 ../scripts/ud_itab.py ../docs/x86/optable.xml .

... from the libudis86/ directory.  The getLabels change here fixes that to be in a defined ordering.

The mergeSSENONE change fixes the ordering differences I see in itab.c between running the above command and similar with python2, by iterating over each table in the same style as used by genOpcodeTable in class UdItabGenerator in scripts/ud_itab.py.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant