Mark Charney e4b1b432b4 xbegin #UDs with 66
Change-Id: Ia94ced4a472c005b89cb80fd08c1a3ca44fedcfe
(cherry picked from commit 20855608232d6cf5cd2f33e0563b0545a8ba9623)
2017-06-29 22:16:45 -04:00
2017-06-29 22:16:45 -04:00
2017-06-12 14:41:25 -04:00
2017-06-29 22:16:38 -04:00
2017-06-12 14:41:25 -04:00
2016-12-16 16:09:38 -05:00
2016-12-23 11:38:57 -05:00
2017-06-12 14:41:22 -04:00

Intel X86 Encoder Decoder (Intel XED)

Doxygen API manual and source build manual:

https://intelxed.github.io

Bugs:

Intel internal employee users/developers:

http://mjc.intel.com

Everyone else:

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

Abbreviated 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:/python27/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 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.
Description
⚠️ ARCHIVED: Original GitHub repository no longer exists. Preserved as backup on 2026-01-31T05:30:08.753Z
Readme 1.5 MiB
Languages
Python 66.7%
C 33.3%