Skip to content

intelxed/xed

main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

Updated CPUs and instructions according to ISE (Intel Architecture Instruction Set Extensions
and Future Features) rev-046, September 2022.

Added:
  - Added new chips: Granite Rapids, Sierra Forest, Grand Ridge and Lakefield
  - Added new Instructions: AMX-FP16, AVX-IFMA, AVX-NE-CONVERT, AVX-VNNI-INT8, CMPCCXADD,
     ICACHE_PREFETCH, MSRLIST, RAO-INT and WRMSRNS
  - Added getter API for VEX.pp prefix encoding value

Fixed:
  - Fixed instructions-set list for SPR
  - Fixed first operand access definition for SSE compute instructions (#287)

Modified:
  - Internal core modifications and updates
9fc12ab

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Intel X86 Encoder Decoder (Intel XED)

.github/workflows/ci.yml

Doxygen API manual and source build manual:

https://intelxed.github.io

Bugs:

https://github.com/intelxed/xed/issues/new

Abbreviated GITHUB building instructions:

git clone https://github.com/intelxed/xed.git xed
git clone https://github.com/intelxed/mbuild.git mbuild
cd xed
./mfile.py

then get your libxed.a from the obj directory. Add " --shared" if you want a shared object build. Add " install" if you want the headers & libraries put in to a kit in the "kits" directory. Add "C:/python3/python " before "./mfile.py" if on windows.

How to build the examples:

There are two options:

  1. When building libxed you can also build the examples, from the main directory (above examples):
./mfile.py examples

and the compiled examples will be in obj/examples.

  1. Build a compiled "kit" and the build the examples from within the kit:
./mfile.py install
cd kits
cd <whatever the kit is called>
cd examples
./mfile.py

See source build documentation for more information.

Binary size?

Concerned about large libraries or binaries? There are several options:

  1. Consider building with "--limit-strings"
  2. Strip the binaries
  3. Consider doing an encoder-only or decoder-only build if you only need one or the other.