c4f

KO | EN

gitlite — search

#hacktoberfest #react #typescript #llm #go #golang #android #linux #java #windows #kubernetes #vue #awesome-list #openai

(★ 15)

The C4 Concurrent C Fuzzer

c4f 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# _c4f_: the C4 fuzzer

![Main workflow](https://github.com/c4-project/c4f/workflows/Main%20workflow/badge.svg)

_c4f_ (previously known as `act`)
is a 'fuzzer' over C litmus tests of a format broadly compatible with
that produced by [memalloy](https://github.com/JohnWickerson/memalloy)
and consumed by [herdtools7](https://github.com/herd/herdtools7).
It takes initial litmus tests, and performs transformations to them
that complicate their compilation while (hopefully!) preserving the
soundness of the initial test's postcondition.

Other parts of the C4 project include:

- [c4t](https://github.com/c4-project/c4t),
  for running automated compiler tests using _c4f_;
- [c4-scripts](https://github.com/c4-project/c4-scripts),
  for doing various tasks that _c4f_ and _c4t_ are too low-level to do
  comfortably;
- [c4-corpora](https://github.com/c4-project/c4-corpora),
  a set of Memalloy-generated inputs that can be used with _c4f_.

## Licence and Acknowledgements

- The overall _c4f_ project, and all original code, is licenced under
  the MIT licence: see `LICENSE`.

- The C lexer and parser are based on those from
  [herdtools7](https://github.com/herd/herdtools7).  We include these in
  _c4f_ under the provisos of herd's
  [CECILL-B](http://www.cecill.info/licences/Licence_CeCILL-B_V1-en.html)
  licence: see `LICENSE.herd`. _(This is not an
  official endorsement by the Herd team of this project.)_

## Included programs

_c4f_ consists of two programs:

- `c4f`, the fuzzer itself, with commands to run the fuzzer, replay fuzzer traces,
  and bisect fuzzer traces;
- `c4f-c`, a toolset for interpreting C litmus tests and dumping them to executable C.

Each command has various subcommands, including the `help` command: for example,
`c4f help` will tell you information about which subcommands the fuzzer has.

## Building and running

**NOTE:**
_c4f_ uses Jane Street's `core` library, which only works properly on
POSIX-style operating systems.  If you're using Windows, consider
using WSL, or Cygwin, etc.

There are two main ways to build and run _c4f_:

- run `opam install .` (or `make install`) to install it on your machine as a pinned OPAM package;
  then, if your OPAM switch is in PATH, just run the tools directly;
- run its commands as `dune exec TOOLNAME -- ...`; this will automatically build _c4f_
  for you when needed, but won't work well with _c4f_'s scripts, and won't
  automatically install dependencies. (The `--` is needed to stop `dune` from
  trying to parse the arguments itself.)

You can also manually build _c4f_ using `dune build`, or
`make` (which just calls the former).

### Preparation

_c4f_ optionally accepts a configuration file listing fuzzer parameters.  If
you're using _c4t_, it sets up the configuration itself; if not, check
`c4f.conf.example` for an idea of what goes in such a file, and use `-config
PATH` to supply one.

### Basic usage

To test whether _c4f_ is installed and working, you can try:

```shell
$ git clone https://github.com/c4-project/c4-corpora /path/to/corpora
$ c4f run /path/to/corpora/partialSC/small/test_8.litmus
```

(or `dune exec c4f -- run`, per above)

This should output some truly horrendous C to stdout.  (You can
experiment with the other `test_X.litmus` files in that directory,
supply your own Litmus test, or add `-o path.litmus` to write to a
file.)

c4f

c4f 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

c4f

c4f 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README