add please to sdk

If I rattle on the keyboard I get ControlLeft coming up regularly, even though I am far from the control keys. Upgrading pc_keyboard to 0.5.0 seems to fix it.

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(

The default documentation URL points to github.com. Doing this in VS2017 results in a message from github that internet explorer is an unsupported browser.

Workaround is to use local storage/clone of the wiki.

COPYING and README claim this is GPL, but it doesn't specify which version exactly? It looks like GPLv2, the question is: "GPLv2 only" or "GPLv2 or later"?
The current uc.c only contains a copyright where it's unclear wether that file also belongs to GPL'd code.
The source files or README should contain [the license text as per COPYING file](https://github.com/unicorn-engine/unicorn/blob/master/CO

Just a suggestion to add a "--help" support to benchdnn.
As today benchdnn does nt seem to have a --help support, the doc being only available online on this page:
https://github.com/intel/mkl-dnn/tree/master/tests/benchdnn
the proposal is to add a minimum of "print usage" to the benchdnn CLI tool.

Environ

While the test_suite presented in #589 does work, it is still pretty simple and can be improved and enhanced.

• Add tests for gnutils and coreutils.
• Add necessary utilities so more complex programs can be compiled from sources.
• Integrate CMake, so one could write something like make validate and the subset of test that is deemed necessary (for example everything with min t

I wonder why nobody every asked for this, shouldn't this be a common feature?
This feature would reduce tediousness when having to run multiple "Fill with NOPs" or "Fill with 00s" or "Binary Edit".

The documentation should always be in sync with the latest changes. Currently, this involves me manually building it and pushing it into an S3 bucket. That could happen automatically through CI.

Additionally, it would be great if we could display a drop-down in the doc that allows viewing documentation for older versions of Zydis as well, similar to what docs.rs does for Rust

RETURN pseudo-instruction currently accepts only constant values.

• RETURN should accept general-purpose registers for functions with integer or pointer return type. Lower to STORE.RESULT for Go and to MOV[ZX/SX](rax/eax, reg) for other ABIs
• RETURN should accept xmm registers for functions with floating-point return type. Lower to STORE.RESULT for Go and to MOVSS/MOVSD(xmm0, xmmN)

Consider porting existing PeachPy Go projects to avo. At a minimum this would be really valuable feedback and system-level testing for avo. These could be committed to the avo examples directory or potentially committed back to the original repos if their maintainers are interested.

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.

After running NC with NCP for more then a year with over 2 million files stored on it, I asked myself if the mysql/mariadb DB needs to be maintained?
I searched the internet and the simplest solution I found was using

sudo mysqlcheck -o --all-databases

This reduced the DB size from around 950MB to a little over 800MB and NC seems to be a little more responsive (but this could homeopat

Just like clicking on a function takes you to its definition, clicking on a struct reference like STR_4231 * pStruct = NULL; should take you to the definition of STR_4321