Now when oss-fuzz provides pretty code coverage, it is easy to see which parts of the code are not fuzzed properly.
Identify what can be done, and add fuzzers targeting the uncovered code.

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(

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

该项目已由国际合作团队接管, 为及时回复, 请使用英文交流.

This project has been taken over by the international cooperation team. In order to respond promptly, please use English to communicate.

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.

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

Raising scalars and vectors to integer powers is very common (e.g. llvm.powi), so I think the following APIs would be very useful:

• double Sleef_ipow_u10(double x, int32_t y);
• __m128d Sleef_ipowd2_u10(__m128d x, int32_t y);
• __m256d Sleef_ipowd4_u10(__m256d x, int32_t y);
• __m512d Sleef_ipowd8_u10(__m512d x, int32_t y);
• floa

What would you like to be added:

The "Getting Started" documentation assumes that a cluster already exists to configure the cluster.yml file.

Why is this needed:

The instructions in https://pharos.sh/docs/getting-started.html#prepare-nodes-for-kubernetes-cluster are insufficient. What do I do with the

current C/C++ API list only update to n4842 and n2455.

C++20 latest draft (see https://en.cppreference.com/w/cpp/links): https://isocpp.org/files/papers/N4860.pdf
C2x latest draft (see https://en.cppreference.com/w/c/links): http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2479.pdf

CI/CD on Google Cloud

Look over to Tensorflow Official Build Status.

We can have different badges for different mediums of deployment by using Google Cloud.