You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
xed_utils provides several Python scripts for organizing and displaying the x86 instruction encoding information contained in Intel XED, including an x86 opcode map generator:
I also have a related request: Would it be possible to add an option to xed/mfile.py to terminate XED build immediately after all relevant data files have been collected into obj/dgen? This would remove the dependence on the C compiler from a tool like xed_utils which only needs the files in obj/dgen.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
xed_utils provides several Python scripts for organizing and displaying the x86 instruction encoding information contained in Intel XED, including an x86 opcode map generator:
https://github.com/ctchou/xed_utils
Could you add a pointer to it to the Community Extensions page?
https://github.com/intelxed/xed/wiki/Community-Extensions-for-Intel-XED#contributing-to-this-page
I also have a related request: Would it be possible to add an option to xed/mfile.py to terminate XED build immediately after all relevant data files have been collected into obj/dgen? This would remove the dependence on the C compiler from a tool like xed_utils which only needs the files in obj/dgen.
Thanks in advance!
The text was updated successfully, but these errors were encountered: