radareorg/r2hexagon

Hexagon disassembler code generator from the official instruction manual.

Overview

This is a Hexagon disassembly and analysis plugin generator for radare2. It uses text file of the specification as a source (recognized from PDF file), and some additional text files with some amendments.

It processes the files and generate C code in r2 directory. Just run importer.py.

The parsing part based largely on hexag00n importer.

Contributors

• Anton Kochkov

• Lucas Molas

• Iván Arce

• Juan Heguiabehere

• Christian Heitman

• D.C.

r2hexagon's Issues

Inconsistent C-files when executing import.py multiple times

There seems to be a weird bug in the script. At least on my machine the generated hexagon_disas.c stays not consistent over multiple executions of the script:

$> git clone https://github.com/radareorg/r2hexagon && cd r2hexagon
$> ./import.py > /dev/null
$> git diff --numstat r2/hexagon_disas.c
$> 
$> ./import.py > /dev/null
$> git diff --numstat r2/hexagon_disas.c
8       9       r2/hexagon_disas.c
$>
$> ./import.py > /dev/null
$> git diff --numstat r2/hexagon_disas.c
32      33      r2/hexagon_disas.c

Try it again.

$> git clone https://github.com/radareorg/r2hexagon && cd r2hexagon
$> ./import.py > /dev/null
$> git diff --numstat r2/hexagon_disas.c
10      10      r2/hexagon_disas.c

$> ./import.py > /dev/null
$> git diff --numstat r2/hexagon_disas.c
33      33      r2/hexagon_disas.c

Compare results with other Hexagon disassemblers

• https://github.com/n-o-o-n/idp_hexagon

Probably add more tests in https://github.com/radareorg/radare2/blob/master/test/db/asm/hexagon

const_extenders.txt is missing instructions

The const_extenders.txt file is missing some instructions which therefor get not extended through immext(#u26).
This leads occasionally to disassembly like that:

Which is not correct because the immext() instruction is always applied to the following instruction (see: Chapter 10.9 - Constant extenders Reference Manual V62)

The const_extenders.txt looks generated. @XVilka Is this is the case?
If so, can you push it please?

Add support for post-v62 instructions as well as HVX.