High level conclusions

Fuzzer fuzz_asm_arm64_arm is blocked:

The runtime code coverage of fuzz_asm_arm64_arm covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_hex is blocked:

The runtime code coverage of fuzz_asm_hex covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_arm_thumb is blocked:

The runtime code coverage of fuzz_asm_arm_thumb covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_systemz is blocked:

The runtime code coverage of fuzz_asm_systemz covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_sparcbe is blocked:

The runtime code coverage of fuzz_asm_sparcbe covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_ppc64 is blocked:

The runtime code coverage of fuzz_asm_ppc64 covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_armv8_arm is blocked:

The runtime code coverage of fuzz_asm_armv8_arm covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_evm is blocked:

The runtime code coverage of fuzz_asm_evm covers 0.0% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_ppc32be is blocked:

The runtime code coverage of fuzz_asm_ppc32be covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_sparc is blocked:

The runtime code coverage of fuzz_asm_sparc covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_x86_16 is blocked:

The runtime code coverage of fuzz_asm_x86_16 covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_mips is blocked:

The runtime code coverage of fuzz_asm_mips covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_mips64 is blocked:

The runtime code coverage of fuzz_asm_mips64 covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_riscv64 is blocked:

The runtime code coverage of fuzz_asm_riscv64 covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_ppc64be is blocked:

The runtime code coverage of fuzz_asm_ppc64be covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_arm_armv8be is blocked:

The runtime code coverage of fuzz_asm_arm_armv8be covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_x86_32 is blocked:

The runtime code coverage of fuzz_asm_x86_32 covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_sparc64be is blocked:

The runtime code coverage of fuzz_asm_sparc64be covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_arm_armbe is blocked:

The runtime code coverage of fuzz_asm_arm_armbe covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_arm_arm is blocked:

The runtime code coverage of fuzz_asm_arm_arm covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_arm_thumbv8be is blocked:

The runtime code coverage of fuzz_asm_arm_thumbv8be covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_arm_thumbv8 is blocked:

The runtime code coverage of fuzz_asm_arm_thumbv8 covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_arm_thumbbe is blocked:

The runtime code coverage of fuzz_asm_arm_thumbbe covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_x86_64 is blocked:

The runtime code coverage of fuzz_asm_x86_64 covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_mipsbe is blocked:

The runtime code coverage of fuzz_asm_mipsbe covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_riscv32 is blocked:

The runtime code coverage of fuzz_asm_riscv32 covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzer fuzz_asm_mips64be is blocked:

The runtime code coverage of fuzz_asm_mips64be covers 5.691% of its statically reachable code. This means there is some place that blocks the fuzzer to continue exploring more code at run time.

Fuzzers reach 1.535% of cyclomatic complexity.

Fuzzers reach 0.794% of all functions.

Reachability and coverage overview

Functions statically reachable by fuzzers

33 / 4152

Cyclomatic complexity statically reachable by fuzzers

204 / 13287

Runtime code coverage of functions

111 / 4152

Warning: The number of runtime covered functions are larger than the number of reachable functions. This means that Fuzz Introspector found there are more functions covered at runtime than what is considered reachable based on the static analysis. This is a limitation in the analysis as anything covered at runtime is by definition reachable by the fuzzers.
This is likely due to a limitation in the static analysis. In this case, the count of functions covered at runtime is the true value, which means this is what should be considered "achieved" by the fuzzer.

Use the project functions table below to query all functions that were not covered at runtime.

The following table shows data about each function in the project. The functions included in this table correspond to all functions that exist in the executables of the fuzzers. As such, there may be functions that are from third-party libraries.

For further technical details on the meaning of columns in the below table, please see the Glossary .

Func name	Functions filename	Args	Function call depth	Reached by Fuzzers	Runtime reached by Fuzzers	Combined reached by Fuzzers	Fuzzers runtime hit	Func lines hit %	I Count	BB Count	Cyclomatic complexity	Functions reached	Reached by functions	Accumulated cyclomatic complexity	Undiscovered complexity

Fuzzer: fuzz_asm_mips64be

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	9	0.34%
lawngreen	50+	31	1.20%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
383	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	389	ks_open	call site: 00389	InitKs

Runtime coverage analysis

Covered functions

2293

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_mips64be.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_riscv32

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
382	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
3	388	ks_open	call site: 00388	InitKs
2	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

2665

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_riscv32.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_mipsbe

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
383	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	389	ks_open	call site: 00389	InitKs

Runtime coverage analysis

Covered functions

2616

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_mipsbe.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_x86_64

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2533	98.1%
gold	[1:9]	2	0.07%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	3	0.11%
lawngreen	50+	42	1.62%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
5	702	ks_asm	call site: 00702
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392
2	734	ks_asm	call site: 00734
2	737	ks_asm	call site: 00737

Runtime coverage analysis

Covered functions

2592

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_x86_64.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_arm_thumbbe

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	6	ks_open	call site: 00006	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

3192

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_arm_thumbbe.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_arm_thumbv8

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	6	ks_open	call site: 00006	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

3006

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_arm_thumbv8.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_arm_thumbv8be

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	6	ks_open	call site: 00006	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

2633

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_arm_thumbv8be.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_arm_arm

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	6	ks_open	call site: 00006	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

3208

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_arm_arm.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_arm_armbe

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	6	ks_open	call site: 00006	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

3043

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_arm_armbe.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_sparc64be

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
381	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	387	ks_open	call site: 00387	InitKs
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

2384

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_sparc64be.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_x86_32

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2533	98.1%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	3	0.11%
lawngreen	50+	43	1.66%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
5	702	ks_asm	call site: 00702
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392
2	734	ks_asm	call site: 00734
2	737	ks_asm	call site: 00737

Runtime coverage analysis

Covered functions

2765

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_x86_32.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_arm_armv8be

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	6	ks_open	call site: 00006	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

3119

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_arm_armv8be.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_ppc64be

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
384	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

2481

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_ppc64be.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_riscv64

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
382	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
3	388	ks_open	call site: 00388	InitKs
2	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

2663

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_riscv64.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_mips64

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
383	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	389	ks_open	call site: 00389	InitKs

Runtime coverage analysis

Covered functions

2742

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_mips64.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_mips

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
383	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	389	ks_open	call site: 00389	InitKs

Runtime coverage analysis

Covered functions

2510

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_mips.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_x86_16

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2533	98.1%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	46	1.78%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
5	702	ks_asm	call site: 00702
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392
2	734	ks_asm	call site: 00734
2	737	ks_asm	call site: 00737

Runtime coverage analysis

Covered functions

2878

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_x86_16.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_sparc

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
381	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	387	ks_open	call site: 00387	InitKs
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

2532

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_sparc.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_ppc32be

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
384	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

2461

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_ppc32be.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_evm

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2580	100.%
gold	[1:9]	0	0.0%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	0	0.0%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
2579	0	EP	call site: 00000	AsmParser::Run

Runtime coverage analysis

Covered functions

8

Functions that are reachable but not covered

123

Reachable functions

123

Percentage of reachable functions covered

0.0%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_evm.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_armv8_arm

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	6	ks_open	call site: 00006	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

2943

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_armv8_arm.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_ppc64

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
384	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

2404

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_ppc64.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_sparcbe

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
381	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	387	ks_open	call site: 00387	InitKs
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

2249

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_sparcbe.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_systemz

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2540	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	9	0.34%
greenyellow	[30:49]	29	1.12%
lawngreen	50+	1	0.03%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
380	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	386	ks_open	call site: 00386	InitKs
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

1969

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_systemz.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_arm_thumb

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
385	6	ks_open	call site: 00006	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001
2	392	ks_open	call site: 00392

Runtime coverage analysis

Covered functions

3194

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_arm_thumb.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_hex

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
379	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
6	385	ks_open	call site: 00385	InitKs
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

2916

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_hex.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1

Fuzzer: fuzz_asm_arm64_arm

Call tree

The calltree shows the control flow of the fuzzer. This is overlaid with coverage information to display how much of the potential code a fuzzer can reach is in fact covered at runtime. In the following there is a link to a detailed calltree visualisation as well as a bitmap showing a high-level view of the calltree. For further information about these topics please see the glossary for full calltree and calltree overview

Call tree overview bitmap:

The distribution of callsites in terms of coloring is

Color	Runtime hitcount	Callsite count	Percentage
red	0	2539	98.4%
gold	[1:9]	1	0.03%
yellow	[10:29]	0	0.0%
greenyellow	[30:49]	0	0.0%
lawngreen	50+	40	1.55%
All colors	2580	100

Fuzz blockers

The following nodes represent call sites where fuzz blockers occur.

Amount of callsites blocked	Calltree index	Parent function	Callsite	Largest blocked function
1823	741	ks_asm	call site: 00741	AsmParser::parseStatement
378	5	ks_open	call site: 00005	InitKs
290	408	ks_asm	call site: 00408	MCObjectFileInfo::initMachOMCObjectFileInfo
7	384	ks_open	call site: 00384	InitKs
6	709	ks_asm	call site: 00709
6	734	ks_asm	call site: 00734	AsmParser::initializeDirectiveKindMap
5	702	ks_asm	call site: 00702
4	396	ks_option	call site: 00396
4	403	LLVMFuzzerTestOneInput	call site: 00403	EVM_opcode
4	716	ks_asm	call site: 00716
4	723	ks_asm	call site: 00723
2	1	LLVMFuzzerTestOneInput	call site: 00001

Runtime coverage analysis

Covered functions

2692

Functions that are reachable but not covered

116

Reachable functions

123

Percentage of reachable functions covered

5.69%

NB: The sum of covered functions and functions that are reachable but not covered need not be equal to Reachable functions . This is because the reachability analysis is an approximation and thus at runtime some functions may be covered that are not included in the reachability analysis. This is a limitation of our static analysis capabilities.

Warning: The number of covered functions are larger than the number of reachable functions. This means that there are more functions covered at runtime than are extracted using static analysis. This is likely a result of the static analysis component failing to extract the right call graph or the coverage runtime being compiled with sanitizers in code that the static analysis has not analysed. This can happen if lto/gold is not used in all places that coverage instrumentation is used.

Function name	source code lines	source lines hit	percentage hit

Files reached

filename	functions hit
suite/fuzz/fuzz_asm_arm64_arm.c	14
llvm/keystone/ks.cpp	48
llvm/lib/Support/Triple.cpp	47
llvm/lib/Support/StringRef.cpp	12
llvm/include/llvm/ADT/MapVector.h	10
llvm/include/llvm/ADT/SmallVector.h	25
llvm/include/llvm/ADT/SetVector.h	5
llvm/include/llvm/ADT/Triple.h	10
llvm/include/llvm/ADT/StringRef.h	9
llvm/lib/Support/TargetRegistry.cpp	10
llvm/lib/Support/TargetParser.cpp	1
llvm/lib/Support/Twine.cpp	1
llvm/include/llvm/Support/TargetRegistry.h	15
llvm/lib/MC/SubtargetFeature.cpp	13
llvm/keystone/EVMMapping.cpp	2
llvm/lib/MC/MCObjectFileInfo.cpp	32
llvm/include/llvm/MC/SectionKind.h	1
llvm/lib/Support/MemoryBuffer.cpp	18
llvm/include/llvm/Support/ErrorOr.h	3
llvm/include/llvm/Support/SourceMgr.h	4
llvm/lib/MC/MCParser/MCAsmParser.cpp	3
llvm/lib/MC/MCParser/AsmParser.cpp	239
llvm/include/llvm/MC/MCSection.h	1
llvm/lib/MC/MCParser/MCAsmLexer.cpp	2
llvm/lib/MC/MCExpr.cpp	41
llvm/include/llvm/Object/ObjectFile.h	4
llvm/include/llvm/MC/MCSymbol.h	9
llvm/include/llvm/MC/MCParser/MCAsmLexer.h	3
llvm/include/llvm/ADT/Twine.h	10
llvm/include/llvm/Support/raw_ostream.h	3
llvm/include/llvm/ADT/APInt.h	10
llvm/include/llvm/Support/MathExtras.h	1
llvm/lib/Support/APInt.cpp	18
llvm/include/llvm/ADT/APFloat.h	8
llvm/lib/Support/APFloat.cpp	90
llvm/lib/MC/MCSectionELF.cpp	1
llvm/include/llvm/MC/MCAsmBackend.h	1
llvm/lib/MC/MCAssembler.cpp	8
llvm/lib/MC/MCFragment.cpp	23
llvm/include/llvm/Object/ELFTypes.h	1