arno
/
bddisasm
mirror of https://github.com/bitdefender/bddisasm.git
1
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'ee6cdd6cb6'
${ noResults }
bddisasm/isagenerator/instructions
History
BITDEFENDER\vlutas ee6cdd6cb6
Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 		1 year ago
..
cpuid.dat Switched from nil to n/a naming for absent operands, as it is more obvious. 1 year ago
flags.dat Switched from nil to n/a naming for absent operands, as it is more obvious. 1 year ago
modes.dat Switched from nil to n/a naming for absent operands, as it is more obvious. 1 year ago
table_0F.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_0F_3A.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_0F_38.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_3dnow.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_base.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_evex1.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_evex2.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_evex3.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_evex5.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_evex6.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_fpu.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_vex1.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_vex2.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_vex3.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago
table_xop.dat Switched to a more parsing-friendly format for the instructions database, where individual components are sepparated by a semicolon. 1 year ago