mirror of
https://github.com/RPCSX/xed.git
synced 2026-01-31 01:05:17 +01:00
4ce1e23c9a
* for broadcast instructions and AVX512 ld-op instr with embedded
broadcast being used.
* xed_decoded_inst_is_broadcast_instruction(xedd) for pure broadcasts
* xed_decoded_inst_uses_embedded_broadcast(xedd) for AVX512 ld-op with embedded broadcast
* xed_decoded_inst_is_broadcast(xedd) for logical OR of the above two functions.
Change-Id: Icb8a0e20380156239be712a2542477fd79222fd9
(cherry picked from commit 2a4532c07443ba22db49ad9e21887a935ca52b1f)
Intel X86 Encoder Decoder (Intel XED)
Doxygen API manual and source build manual:
Bugs:
Intel internal employee users/developers:
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:
-
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.
-
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:
- Consider building with "--limit-strings"
- Strip the binaries
- Consider doing an encoder-only or decoder-only build if you only need one or the other.