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.

See #4243. We can use hccap/hccapx files, but normally I'd recommend using wpapcap2john if you do have a pcap at all. That, or (possibly even better) something from hcxtools which we could also mention (Zerobeat's hcxdumptool is the absolute best sniffer for WPA as well).

See #158 for context.

1. Game Boy Crib Sheet - A handy printable reference sheet with ASM opcodes, memory locations, and much more (repository).
2. OP Codes cheatsheet
3. [gb-opcodes](https://gbdev.g

Hi,

I know I am reopening an old discussion that has been already discussed here (#1032 or #162), but this is the one thing that make miasm hard to use. So I wonder if the issue with it is :

1. Not enough time to write it ?
2. The API is changing too often too create a documentation that stays up to date ?

If it is 1, I think it should be possible to have some other people involved and

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)

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.

The machine the wiki is on:

• Is old and slow
• Costs @suborb money every month
• Only @suborb has access to

Steps to do this:

• Enable wiki on the GitHub project
• Run the migration script
• Upload the wiki
• Fix up any migration errors
• Move examples into examples directory in the main repo
• Provide a redirect script on z88dk.org so google links remain

Adding background to list of syntax styling of editor would allow to use dark syntax themes (like Solarized Dark)

Currently codegen and IR are both in the same g8/ir package. They should be separated so that it is easier to port to x86 and arm platforms in the future.

The fp_reduction_latency benchmarks were the very first benchmark, optimization and primitive code tested in Laser.

Unfortunately it is currently very confusing.

It should be reorganized:

• 1. Multiple accumulators: https://github.com/numforge/laser/blob/af191c086b4a98c49049ecf18f5519dc6856cc77/benchmarks/fp_reduction_latency/reduction_bench.nim and https://github.com/numforge/laser/blo

When reading https://ppci.readthedocs.io/en/latest/reference/codegen/registerallocator.html , I was surprised that corresponding .rst file is almost empty: https://github.com/windelbouwman/ppci-mirror/blob/master/docs/reference/codegen/registerallocator.rst , and the contents comes fully from the corresponding .py module, https://github.com/windelbouwman/ppci-mirror/blob/master/ppci/codegen/regist