arno/bddisasm
1
0
Fork 0
mirror of https://github.com/bitdefender/bddisasm.git synced 2024-11-13 02:48:59 +00:00
Code Issues Releases Wiki Activity
dac2092c17
bddisasm/bddisasm_test
History
BITDEFENDER\vlutas 433e723e07 Implemented a reverse oprand lookup table. It holds pointers to relevant operands inside INSTRUX, for quick lookup. 
Moved helper functions in bdhelpers.c.
Added a dedicated BranchInfo field inside INSTRUX, containing the most relevant branch information.
2021-11-02 11:22:22 +02:00
..
amx Added support for TDX instructions, per https://software.intel.com/content/dam/develop/external/us/en/documents/intel-tdx-cpu-architectural-specification.pdf. 2020-09-10 11:06:20 +03:00
avx Added support for UINTR, HRESET and AVX-VNNI instructions, as per Intel® Architecture Instruction Set Extensions Programming Reference 41 (October 2020). 2020-10-05 13:19:03 +03:00
avx512 Multiple changes 2021-07-08 12:40:39 +03:00
basic Implemented a reverse oprand lookup table. It holds pointers to relevant operands inside INSTRUX, for quick lookup. 2021-11-02 11:22:22 +02:00
cet Multiple improvements 2021-08-31 13:37:50 +03:00
fred Implemented a reverse oprand lookup table. It holds pointers to relevant operands inside INSTRUX, for quick lookup. 2021-11-02 11:22:22 +02:00
kl Added support for Intel Key Locker instructions, as per https://software.intel.com/content/www/us/en/develop/download/intel-key-locker-specification.html. 2020-09-16 11:56:05 +03:00
simd Fixed https://github.com/bitdefender/bddisasm/issues/38. 2021-01-15 19:09:53 +02:00
special Removed old test files. 2021-08-31 13:49:29 +03:00
tdx Updated SEAMCALL specs according to Intel® Trust Domain CPU Architectural Extensions 343754-002US May 2021. 2021-05-31 13:34:52 +03:00
uintr Implemented a reverse oprand lookup table. It holds pointers to relevant operands inside INSTRUX, for quick lookup. 2021-11-02 11:22:22 +02:00
README.md Initial commit. 2020-07-21 11:19:18 +03:00
test_all.py Multiple changes 2021-07-08 12:40:39 +03:00

README.md

Disassembler Tests

These tests are used to validate bddisasm. Each test consists of up to three files:

  • The binary test file. The name format for this type of file is name_16|32|64. No extension must be provided; 16/32/64 indicates disassembly mode
  • The output result file. Must be named the same as the binary test file, but with the extension .result
  • Optional assembly file, used to generate the binary test file

The test_all.py script will iterate all the test folders, and it will run bddisasm on each identified test file. The result file will be compared with the output of the test run. If they are not the same, the test will fail. Note that bddisasm will be run with the -exi option, in order to dump all possible information about the instructions.

NOTE: This test will assume disasm is in the path. Works on Windows only.