Skip to content

Commit

Permalink
Add links to make documentation more discoverable and fix typos.
Browse files Browse the repository at this point in the history
PiperOrigin-RevId: 715856285
hanyangtay authored and copybara-github committed Jan 15, 2025
1 parent 57a5090 commit fc7a802
Showing 2 changed files with 5 additions and 6 deletions.
7 changes: 4 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -31,7 +31,7 @@ information from the target.
By applying fuzzing techniques to a proxy, we can generate a series of test
inputs (corpus) that produce interesting behavior in the proxy. Our underlying
assumption is that this translates into similarly interesting behavior in the
target.
target. Read more in the [docs](https://github.com/google/silifuzz/blob/main/doc/proxy_architecture.md).

##### Corpus / Corpus shard

@@ -50,7 +50,8 @@ microseconds, but it can be arbitrarily large. Snapshots are stored as

Snapshots are typically created from the inputs generated by a fuzzing engine.
For CPU testing purposes these inputs are filtered to eliminate all
non-deterministic snapshots.
non-deterministic snapshots. Read more in the
[docs](https://github.com/google/silifuzz/blob/main/doc/what_makes_a_good_test.md).

###### Expected end state

@@ -67,7 +68,7 @@ in-memory one except that native pointers are replaced with offsets. See this
[header](https://github.com/google/silifuzz/blob/main/snap/gen/relocatable_snap_generator.h)
for details. This format is often referred to as *relocatable*. Each Snap
contains exactly one expected end state i.e. Snaps are
microarchitecture-specific.
microarchitecture-specific. Read more in the [docs](https://github.com/google/silifuzz/blob/main/doc/snap.md).

##### Runner

4 changes: 1 addition & 3 deletions doc/snap.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,4 @@
# Silifuzz Snap Data Structurue

[TOC]
# Silifuzz Snap Data Structure

## Overview

0 comments on commit fc7a802

Please sign in to comment.