Env:

• python 3.8
• capstone 4.0.1
• ubuntu 18.04 (WSL)

Repro:

import capstone
md = capstone.Cs(capstone.CS_ARCH_X86, capstone.CS_MODE_32)
md.detail = True

# case 1
# expected: fstcw  WORD PTR [ebp-0x4] (based on Objdump disassembly which round-trips with GNU as)
for insn in md.disasm(b"\x9B\xD9\x7D\xFC", 0):
    print(insn.address, insn.mnemonic, insn.op_str)

print(

xargo CI is failing with a strange ICE:

thread 'rustc' panicked at 'failed to lookup `SourceFile` in new context', src/librustc_middle/ty/query/on_disk_cache.rs:456:17

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpect

Just a quick question, do you think we should add a flag to keystone that will log all assemble attempts and their results? This could help for detecting inconsistencies, however it might be out of the scope for the project.

Our documentation site is always lagging behind as updating the docs is a non-trivial task that has to be automated. Setting up the Travis job for building wouldn't be trivial (we probably won't fit into the time constraints), but we can use GitHub actions and host a documentation builder on one of our servers. We shall update both bap documentation and Primus Lisp docs.

Hello,
Do you know about Conan?
Conan is modern dependency manager for C++. And will be great if your library will be available via package manager for other developers.

Here you can find example, how you can create package for the library.

If you have any questions, j

We should add WASM simd128 implementations of as many SSE/SSE2/etc. functions as possible.

Some of the functions won't see much, if any, improvements since we already have GCC-style vector extension and OpenMP SIMD support. The real benefit will be for the functions that can't use GCC-style vectors. For example, saturated operations, min/max, etc. And of course there will be a lot of cases w

Need documentation for developers and contributors

For compatibility reasons we probably don't want all of the changes linked via the meta-bug at https://bugzilla.mozilla.org/show_bug.cgi?id=897815 and we don't want to remove the old properties, but we probably do want at least this, or some way to access the properties both directions.

document.body https://bugzilla.mozilla.org/show_bug.cgi?id=1276438 prereq?
https://bugzilla.mozilla.org/sho

See also https://github.com/linuxppc/linux/issues/134